Modifiers and data types about cmdx HOT 2 OPEN

oh i never tried that! and intuitively that's something i wouldn't allow.
it looks like when you do node["translate"] = 5, translate will have [5, 5, 5]. so that's the behaviour i would except for the modifier.

i reproduced the error with garbage result but not consistently. most of the time translate will reset to [0, 0, 0]. in any case it's enough that we have to pay attention

the plug check is very cheap (like 0.6µs/call). with data check it sums up at most to 1µs that's not very expensive for some additional safety (in comparison of the ~45/50µs i have from the setAttr applied from a modifier or even the only ~15/25µs when not applied)

from cmdx.

Agreed, we could consider this not a gotcha but a plain bug.

I should add that..

with cmdx.DagModifier() as mod:
  node = mod.createNode("translate")
  node["translate"] = 0

Would also produce garbage, because any node created within a modifier scope is automatically treated with modifier attribute setters. So the bug-free version of this particular route would be..

with cmdx.DagModifier() as mod:
  node = mod.createNode("translate")

node["translate"] = 0

That is, to exit the modifier first. Or, of course, to use (0, 0, 0).

from cmdx.