New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path objects duplicated in 4.7.1 #3136
Comments
The last time this came up, the fix was to make sure the |
Is there somebody who can take a look at this? As a complete Newbie who hasn't yet got any familiarity with the JMRI code, or even worked out how to build it yet, I'm afraid I wouldn't have a clue where to start looking - I posted this in the hope that my testing feedback would be useful. I guess the only clue is that it must be something that has been changed since 4.6, as the problem wasn't there then. |
Also #682 which seems directly on point. |
Can you regress this on 4.7.2 or .3? If not please close; if so please comment to that effect. TIA. |
I have loaded the panel I am working on into 4.7.1. I was
working on it using JMRI 4.6. It loaded ok and seems to function as normal.
However, when I saved the panel, without making any changes, into a new
file, I noticed that the new XML file has had about 750 lines added by
4.7.1 compared to the one saved by JMRI 4.6, increasing from 12480 to
13226 lines - about a 6% increase.
Doing a diff compare, most of the additions seem to duplicate path
objects within block objects, for example:
The second two path lines were added by the update to 4.7.1, and
duplicate the two path objects that were already there.
I also found some of the duplicated path objects had beansetting
objects. I don't know what these are for, but again they just duplicate
previous path entries:
Again, the second two path objects have been added by 4.7.1 and
duplicate the first two.
I can upload my panel if nobody else can duplicate this problem, but it does reference quite a lot of custom icons which will need to be copied to the right place for the panel to load without errors.
The text was updated successfully, but these errors were encountered: