New issue 139 by macaronikazoo: setKeyable on compound attrs should
propagate to child attrs
http://code.google.com/p/pymel/issues/detail?id=139
well, it'd be nice if it did anyway. so something like:
PyNode( 'persp' ).translate.setKeyable( False )
would set keyable flag on tx, ty and tz to False.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
where does the setKeyable code even exist?
setKeyable is (I believe) auto-wrapped from MFnAttribute.setKeyable... the
auto-wrapping magic happens MetaMayaTypeWrapper, which is the metaclass for
the pymel
Attribute type.
If you're looking to modify the behavior of Attribute.setKeyable, you can
just add a
new method directly to the Attribute class, and have that wrap the
appropriate mel
cmd (setAttr in this case, I think). If there's a hand-defined method, it
will
override any similarly named auto-wrapped command.
...incidentally, there's a number of cases for which it would be nice to
have
propogation-type behavior for attributes... and not just for compound
elements, but
array attributes as well. Unfortunately, this behavior isn't built into
the commands
we wrap, and it's something we haven't gotten around yet to adding
ourselves.
sweet! thanks, I'll see if I can figure something out.
incidentally, who do you get an account here?
I guess I should probably learn how all the unit tests work and whatnot
first - any
data on that? I'm a bit of a unit test n00b... and should absolutely not
be.
Comment #5 on issue 139 by chadrik: setKeyable on compound attrs should
propagate to child attrs
http://code.google.com/p/pymel/issues/detail?id=139
since this is not currently supported by setAttr -keyable, this is being
marked as an
"enhancement", i.e. feature request. it most likely won't make it into
1.0.0, but can be
included in a future release.