You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Partially a bug (maybe a bug in logic) and partially a feature request:
Part 1: Kind of related but didn't want to open a whole ticket for it: clicking the 'Update Model Aliases Using Mapping' button gives no feedback. Some form of 'Done' message would be ideal so you know it's complete and worked.
Part 2: The real issue. There doesn't seem to be a way to assign an old 'submodel name' as an alias to a new model/group. For instance, last year I had a single Wreath with a few submodels. I applied effects to those submodels. This year, I have multiple wreaths so created groups for each of the submodels. I tried manually creating an alias for the group of 'Wreath - 23/Spiral CW' but AutoMap didn't map to it. I then removed my manual alias and manually mapped the old submodel to the new group in the Import Dialog and clicked the 'Update model alias.....' button, which created an alias just as I did.
Arch Model:
Wreath Group:
When I then go back into the Import Dialog and AutoMap, neither the group or the model get the 'old' submodel mapped to them.
The text was updated successfully, but these errors were encountered:
kevinsaucier
changed the title
Importing effects from a submodel to a group using aliases doesn't work as expected
Importing effects from a submodel to a group/model using 'old' aliases doesn't work as expected
Feb 23, 2024
kevinsaucier
changed the title
Importing effects from a submodel to a group/model using 'old' aliases doesn't work as expected
Importing effects from a submodel to a group/model using aliases doesn't work as expected
Feb 23, 2024
@kevinsaucier not that it makes it "right" but can you try without the / or - in the name?
I had my BOAW named MOAW for the longest time and as I'm setting up for 2024 using base folders and cleaning things up, I renamed it and added an alias. Created a new sequnce and Imported one from last year and poof... auto map did mapped MOAW (original name in sequence) to BOAW.
Automap seems to mostly work fine for directly named aliases, including models and alias with - in the name. The issue is when you have a submodel. I can't remove the / from the submodel name because it's a submodel. Am I misunderstanding your request?
derwin12
added a commit
to derwin12/xLights
that referenced
this issue
Mar 13, 2024
Partially a bug (maybe a bug in logic) and partially a feature request:
Part 1: Kind of related but didn't want to open a whole ticket for it: clicking the 'Update Model Aliases Using Mapping' button gives no feedback. Some form of 'Done' message would be ideal so you know it's complete and worked.
Part 2: The real issue. There doesn't seem to be a way to assign an old 'submodel name' as an alias to a new model/group. For instance, last year I had a single Wreath with a few submodels. I applied effects to those submodels. This year, I have multiple wreaths so created groups for each of the submodels. I tried manually creating an alias for the group of 'Wreath - 23/Spiral CW' but AutoMap didn't map to it. I then removed my manual alias and manually mapped the old submodel to the new group in the Import Dialog and clicked the 'Update model alias.....' button, which created an alias just as I did.
Arch Model:
Wreath Group:
When I then go back into the Import Dialog and AutoMap, neither the group or the model get the 'old' submodel mapped to them.
The text was updated successfully, but these errors were encountered: