Bob Jacobsen
Bob Jacobsen
> No, M2S indicates a two event sensor. The MS prefix is exranous. Then that’s your problem. JMRI prefixes require a parseable format: A letter, zero or more digits, then...
`SensorManager` and `TurnoutManager` instances know about the proper prefix for a connection; the GUI (usually) doesn't unless it's gotten it from a `Manager` or some other connection instance. I asked...
> Neither (should) have a prefix. The "address" is two event ids separated by a > semicolon. The OlbcAddress class understands how to deal with that. Then why does adding...
See discussion in #9921
Would you be willing to help do the translation? It's pretty easy, if a bit tedious. The basic process: 1) Download a copy of the properties files from https://github.com/JMRI/JMRI/releases/download/v5.5.7/properties.5.5.7.zip 2)...
The "Adapting to a new language" section on this page might be useful: https://www.jmri.org/help/en/html/doc/Technical/I8N.shtml
I think it's OK to close it. It'll be a while before JMRI moves forward to a Java version where it'll really be relevant, and I'm sure it'll come up...
I believe that the underlying issue was fixed with the SplitEnumVariableValue fix(es) in #11786 and #11790
I've read through this, but I don't understand how to recreate the problem. I haven't been able to with the current head of master, so I'm probably not trying the...
PR #11888 adds a test to make sure this is, and stays, resolved.