-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mover Return Type from Base Not Uniformly 'ApplicationMover' #91
Comments
This is the expected behavior. We had to design the updated interface to be separate from application code which allows for much easier updating of code in the "XTS (Do Not Edit)" folder on existing projects. Because of this we've made the choice to have all base functions return a standard mover. An application mover can be accessed by using the mover index. Please reference this code and specifically line 229 for station 0 in the MAIN.StationLogic Routine. XTS_Base/Base Project/PLC1/POUs/MAIN.TcPOU Lines 225 to 238 in 630ca32
This method will be documented when the branch is published to main as v2.0 |
Reopened. I want to look into this one again. The workaround feels clunky to me. |
On the Mediator feature branch, the ApplicationMover object was added to aide in separating out the base code from user modified/extended application code. With this, the return types inside the Base classes return 'ApplicationMover' and not 'Mover'
However, there are a few places that are not returning ApplicationMover and instead are returning Mover. Not an exhaustive list just yet however the spots I've found thus far:
iMoverList.GetMoverByLocation
MoverList.GetMoverByLocation
PositionTrigger.CurrentMover
The text was updated successfully, but these errors were encountered: