If the domain of the Sensor Table window display is restricted to a single
connection (i.e. LCC) the other connections are not checked for a possible
duplicate User Name. Then if the file is saved with a duplicate User Name,
JMRI "hangs" during the reload of the XML file because of a JAVA error. A
warning of a duplicate sensor is given, but it cannot be corrected in JMRI
because the file will not load.
The test was discovered in JMRI 4.7.4ish and the unique name search error
may apply to other entities besides Sensors. I have back up files so I am
not in any jeopardy.
David Parks
Los Altos, CA
