Has there been a change to the way naming conflicts are resolved for CAM setups?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I wrote an add-in that, among other things, renames CAM setups from within a command. On command execute, all setups are assigned their names according to the text in their corresponding text inputs. This has worked fine until one of the recent updates. Now, sometimes the setup names will be appended with a "1". I know this is how Fusion, at least in the CAM environment, resolves name conflicts, where if you try to manually rename a setup to "A" when there is already a setup named "A", the renamed setup will become "A1".
I might have 10 setups in the document- none of which have name conflicts, but upon executing my command, they all get a "1" added to their names. I'm wondering if the bulk-renaming of setups is causing Fusion to think there is a name conflict?
It may have to do with setups having SIMILAR names, like A1, A2, A3, etc. This problem has been inconsistent to reproduce but when it happens it happens to ALL setups, not just ones with similar names.
Anyways if anyone has experienced this or has any insight please let me know.
Thanks