MObjectHandle hashCode... about cmdx HOT 3 CLOSED

Hi @GuidoPollini, thanks and happy to hear you like it. :)

clashes are possible for nodes in the same scene

Indeed, except that leaves out the very next and most important line from the docs.

However different MObjectHandles whose MObjects refer to the same internal Maya object will return the same hash code.

In other words, it always returns the same node in the scene, which is exactly what you want. That's how you can get the same instance of the singleton like this.

instanceA = cmdx.createNode("reverse", name="myNode")
instanceB = cmdx.ls(type="reverse")[0]
assert instanceA is instanceB

Because they will be the same variable.

instanceA._my_special_data = "Hello!"
print(instanceB._my_special_data)
# Hello!

from cmdx.

Indeed:).
if I'm not wrong, in case of clash the Singleton._instance will lose the reference to the original wrapper and (if no cycles are involved) next garbage collection will call Node.del unregistering the callbacks.
It should all be fine:)

from cmdx.

I should hope __del__ is only called when the last reference is lost, rather then once there is a clash. In my code, I call cmdx.uninstall() on scene open to clear out any references and old commands from undo, which is when I expect __del__ to get called.

In practice it has been working well so far. Have been using this for a few years now in all of my Maya projects, most recently/currently ragdoll.

Thanks for double-checking, if you come up with any optimisations or improvements, feel free to share!

from cmdx.