Author Topic: XML Import / Conversion problems due to 2016 releases  (Read 799 times)

Offline jnealand

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
XML Import / Conversion problems due to 2016 releases
« on: March 16, 2016, 06:42:28 PM »
I just discovered this while trying to prepare a presentation for the TN mini this weekend and am posting for others to be aware of.  I'm not saying the change is good or bad, just that it potentially complicates importing an xml based sequence that is shared or just to be imported to a new configuration for this year.

Models and groups are no longer allowed to have the same name so when loading an old v4 sequence you may get error messages if this condition occurs.  You are allowed to rename the model or group or delete them.  I would never delete them, but a rename of the group or the model  can lead to problems in using the sequence if the shared / old sequence used  the one that you renamed.  I have one where a group and a model are both named cascade.  If I rename the model the group will have an error since the model will no longer exist as originally named.  If I rename the group and that name was used in the sequence then I will no longer have that group available under its original name.

Since for a shared sequence I am not the original author and even though I have the original code I cannot easily tell what the proper resolution to this might be.  As of this writing it looks as though a solution will be to closely examine each sequence that you wish to convert using notepad++ and try to decipher which enitity should be renamed – the model or the group.

Another solution might be to install a v4 copy of xlights and load the sequence to see if whether the suspect model or group name was used in building the sequence and making the appropriate modification before trying to import the sequence into your own layout.  In the sequence I tried I got error messages for 3 duplicate names so I at least know what names I need to look at and I may have made the wrong choice in renaming.  I just appended a "grp" to the end of the problem group names and left the model names alone.  Now I have to go back and see if that affected any of the sequence and make changes to the original before I do the import to my own layout.  Just some things to consider.


Jim Nealand
Kennesaw, GA

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: XML Import / Conversion problems due to 2016 releases
« Reply #1 on: March 16, 2016, 07:00:33 PM »
Thanks for the info. Luckily I never named models and groups the same as I thought it was confusing. I did as you said, added Grp to the end.

James

Sent from my SM-G900V using Tapatalk