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
With the introduction of actionable platforms, where all Movables inherit from Actionable (# ), platforms now have both an act() and move() method. This is confusing, especially when using sensor management to task them, and in some cases causes missing functionality if the wrong one is used.
The text was updated successfully, but these errors were encountered:
I think it would make sense to have act() as standard method, and then have move() call act() for backwards compatibility. Aware this isn't a simple fix of just doing this, as the functionality of move() needs to be factored into the act() method with the other possible actions.
With the introduction of actionable platforms, where all
Movable
s inherit fromActionable
(# ), platforms now have both anact()
andmove()
method. This is confusing, especially when using sensor management to task them, and in some cases causes missing functionality if the wrong one is used.The text was updated successfully, but these errors were encountered: