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
Inside the SyncToAxis and SyncToMover calls the gear ratio is locked 1-1. The simple solution for a user that wants to have a non 1-1 gear ratio is to override the method in the Application mover and re-implement in it's entirety. Which is rather cumbersome when only the assignment is all that's needed.
A proposed elegant solution is if the values are already initialized to be 1-1 in the declaration of the Sync function blocks. The user can then extend the SyncToAxis/Mover calls with a new named block (Something like SyncToAxisRatio for example) and then simply call the Super's method
Thoughts? This proposed solution allows for a most users that don't need a 1-1 ratio to continue on as normal and allows users to easily expand if they want access to the optional parameters. This seemed the simplest but open to other ideas/suggestions!
The text was updated successfully, but these errors were encountered:
Inside the SyncToAxis and SyncToMover calls the gear ratio is locked 1-1. The simple solution for a user that wants to have a non 1-1 gear ratio is to override the method in the Application mover and re-implement in it's entirety. Which is rather cumbersome when only the assignment is all that's needed.
A proposed elegant solution is if the values are already initialized to be 1-1 in the declaration of the Sync function blocks. The user can then extend the SyncToAxis/Mover calls with a new named block (Something like SyncToAxisRatio for example) and then simply call the Super's method
Thoughts? This proposed solution allows for a most users that don't need a 1-1 ratio to continue on as normal and allows users to easily expand if they want access to the optional parameters. This seemed the simplest but open to other ideas/suggestions!
The text was updated successfully, but these errors were encountered: