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
Looks like if you try to register two add-ons generated from node trees with the same name, NodeToPython overwrite all the previously stored information about the old add-on. However, it seems like it tries to run the old operator unless you restart Blender.
Attempts could be made to detect if there are any addons/operators with the same name (https://blenderartists.org/t/how-to-know-if-an-operator-is-registered/638803/2). It seems murkier to try and differentiate between if you're just updating an old add-on, or if there are two separate add-ons that happen to share the same name.
For now, I don't think NodeToPython should try to be responsible for resolving these conflicts, but it's not out of the question for a future release
Looks like Blender doesn't like it if you register two add-ons of the same name, investigate further what issues can arise and potential fixes
The text was updated successfully, but these errors were encountered: