The easiest fix for my sorting issue may be to give the turnouts locations based off the turnout numbers. For example 1 through 9 be in a location called Turnouts 1 -9. 10 through 19 location called Turnouts 10 - 19. Etc. Then filter by location when looking for a certain one.
Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------From: "mstevetodd@... [jmriusers]" <jmriusers@...> Date: 3/8/18 10:16 AM (GMT-06:00) To: jmriusers@... Subject: [jmriusers] Re: Turnouts in Engine Driver
?
Hi Kenny,
1. The turnout initial states should match those shown in the JMRI Turnouts Table. Do yours?
This behavior is hardware-dependent. Some systems, such as my LocoNet Tam Valley servo controllers, respond to the startup interrogation with the current state. This updates the Turnout Table, which is then used for EngineDriver. What command station and turnout hardware are you using?
There are some script-based workarounds, for example, when I'm using the Loconet Simulator, I run the SetAllTurnoutsClosed.py script in my startup to force the initial state.
2. The current sort is by UserName. There's a ToDo list item to add an option to sort by SystemName, but it hasn't received any attention. I'm not clear if that would help in your situation. You set your UserName to "Turnout #1"?
As a workaround, you could adjust your UserNames, e.g. "Turnout #01".
For my layout, I use meaningful UserNames, such as "East:Yard Lead". Then I can select "East" as the location and filter my list. This is much easier for me than remembering the assigned addresses.
HTH,
SteveT
