summary so far:
pynode.addAttr('myMulti',dt='string',m=1)
mAttr = pm.PyNode('testNetWorkNode.myMulti')
mAttr[0].set('damn')
works.
pynode.setDynamicAttr('newData',['yo','hey'])
strArryAttr = pm.PyNode('testNetWorkNode.newData')
strArryAttr[0].set('damn')
does not work.
i remember way back around maya 1.5 struggling with alias wavefront
support about how to actually use stringArray or any array attr for
that matter via mel.
i do use them when writing plugins.. but what i am working on now is
not a plugin nor do i want it to be really..
would be nice if pymel wrapped stringArrays to finally behave the same
way stringMultiAttrs do.
particularly since you now have the wonderful setDynamicAttr pynode
function!
or,
at worst, maybe just have the user be able to hint to "setDynamicAttr"
what the resulting type should be when inducing the "addAttr"
behavior. especially when the python data type could logically end up
as more than one maya attr datatype as in the case of stringMulti or
stingArray. they are very similar..
--
http://groups.google.com/group/python_inside_maya
