You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: