Steve,
What you are suggesting certainly should require only an example or two to explain.??
toggle quoted message
Show quoted text
On Tue, May 2, 2023 at 07:36 AM, Steve Todd wrote:
I think the simplest solution is to put the SystemName first, followed by the (optional) User Name. This avoids the need for a delimiter, as I'll simply use the number to split the two.
For the examples provided in your note, the presence of a string of numeral followed by the first blank as the delimiter provides an easy to recognize token.?
That should be OK with most users as the blank following the number would usually be inserted as an almost automatic keystroke typing action and could not get much simpler to understand.??
No matter how we slice and dice this, there is still the expectation that the people in charge of developing the track plan have a good understanding of the AnyRail instructions.? In a club situation with lots of self proclaimed experts, that assumption amounts to "
the best-laid schemes o' mice an' men gang?aft?a-gley."??The AnyRail exported Turnout userNames should be simpler to translate than the Block names turned out to be for me.??
It might be an exceedingly rare prototype situation, but one of our club layout Block userName choices included two instances of the?Low Line AKA the "_" character that caused me to almost completely rewrite my first shared version of the AnyRailBuildBlockSensorList.py script.? And that was without trying to nail down the DCC hardware addresses for the Sensors.
Maybe it would have been smarter for me to have just edited that Sensor by hand??
We are still investigating using LCC hardware for Sensors, Turnouts, and Signals and I have a lot of learning to do before venturing into what that kind of translation that technology would involve.??
The approved "final" track plan has had yet two more revisions in the last week, so I am still spinning my wheels and going nowhere.??
Thanks for keeping me informed,
Cliff
