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
For those of use that use high momentum and rely on braking to stop our locos would you consider taking the BIG BUTTON layout and providing a new layout that replaces the large "STOP" button with a "BRAKE" button. They may need to be another configuration setting where the user has to tell ED which Function number is assigned to new button.
For example, I have standardized on F11 to be the independent brake, using Engine driver with the Big Button layout means I have to look down to select the Brk function key. In ED Function Defaults I have Brk as being the 4th item on the list. I am not copying function labels from JMRI. Right now it is a bit cumbersome using braking with ED. If there is a better way to do this without modifying the app, let me know. Thanks for considering this and all the work the dev team does to make this a very handy application!
The text was updated successfully, but these errors were encountered:
For those of use that use high momentum and rely on braking to stop our locos would you consider taking the BIG BUTTON layout and providing a new layout that replaces the large "STOP" button with a "BRAKE" button. They may need to be another configuration setting where the user has to tell ED which Function number is assigned to new button.
For example, I have standardized on F11 to be the independent brake, using Engine driver with the Big Button layout means I have to look down to select the Brk function key. In ED Function Defaults I have Brk as being the 4th item on the list. I am not copying function labels from JMRI. Right now it is a bit cumbersome using braking with ED. If there is a better way to do this without modifying the app, let me know. Thanks for considering this and all the work the dev team does to make this a very handy application!
The text was updated successfully, but these errors were encountered: