Import Effects -> Save Map -> Merge Mappings

[almostwhitehat]

Is your feature request related to a problem? Please describe.
When using the Save Map function (while importing effects) a new file is created with the current mappings. If the file already exists, it is overwritten with the current mappings.

When importing multiple sequences from vendors, they don't always use the exact same set of props/groups across every individual sequence. This makes the Save & Load Mapping function difficult to use across sequences.

Describe the solution you'd like
If the file already exists, prompt to Overwrite (current behavior) or Merge Mappings (new behavior)

When Merge Mappings is chosen, the current mappings would be merged into the existing file:

• Mappings to props/groups which did not previously have any would be added to the existing file
• Mappings to props/groups which previously had mappings would be overwritten by the new mappings

Describe alternatives you've considered
Without adding any new functionality, this can somewhat be solved by sequence vendors creating a Master demo sequence which contains every prop/group used across their entire selection. Customers could build and save a master mapping against that; which would allow one-click importing of all other sequences from that vendor. This would be cumbersome for both the vendor and customer though.

[derwin12]

Might be possible .. but consider using Aliases. That is the likely the preferred method going forward. Vendors are always tweaking their displays as our the customers (us). Static mappings are only good to a point ..

[computergeek1507]

The mapping files already have a "unused" mappings section, if you import multiple mapping files in the import dialog it will store unused mappings and also put them in the saved file, but it doesn't do the merging on save like you suggested

[almostwhitehat]

Might be possible .. but consider using Aliases. That is the likely the preferred method going forward. Vendors are always tweaking their displays as our the customers (us). Static mappings are only good to a point ..

Good point - Aliases can be helpful here, but there are some shortcomings. Aliases are implicitly global because they are at the Layout layer; but Import Mappings can carry local (vendor-specific) context. This can lead to confusing collisions when a global Alias (eg. Icicles -> Icicle Group) differs from the custom mappings saved for a vendor (eg. Pixel Forest -> Icicle Group)

An ideal solution (though 3 options instead of 2 is never ideal!) would be merging both capabilities (Aliases + Saved Mappings) into one. If Aliases could be easily imported/exported/cleared, we could have vendor-specific aliases with local context for auto mapping.