yeah, thought that. But still it's bad that the property only returns these kind of nodes that are not used anywhere, no?
On Thu, Jul 26, 2012 at 3:13 PM, Ahmidou.xsi <[email protected]> wrote: > It's how was the set data in the moondust alpha, then it was changed. > > > On 26 juil. 2012, at 23:00, Vladimir Jankijevic < > [email protected]> wrote: > > hello list, > > I was looking something up in the docs and found something I never saw > before. I was trying to get all the setData nodes in a specific compound > and thought I could use the counterpart of the DataProviderNodes property, > namely the DataModifierNodes. Testing this on a simple ICETree led to > fails. So I wondered if I did something wrong and executed their python > sample script. To my surprise this script worked. But the weird thing is > what it generated. If you look into the ICETree it generates, you'll find a > Set Data node that has a really strange interface (a ancient node?). Has > anybody ever used this node? > Tell me what you think. > > > http://download.autodesk.com/global/docs/softimage2013/en_us/sdkguide/index.html?url=si_om/ICEDataModifierNode.html,topicNumber=si_om_ICEDataModifierNode_html > > Oh, and while we're on this topic, why doesn't the DataModifierNodes > property return the 'Set One Data' nodes?????? How are we supposed to get > them other than through their type? > > Cheers > Vladimir > > -- > --------------------------------------- > Vladimir Jankijevic > Technical Direction > > Elefant Studios AG > Lessingstrasse 15 > CH-8002 Zürich > > +41 44 500 48 20 > > www.elefantstudios.ch > --------------------------------------- > > -- --------------------------------------- Vladimir Jankijevic Technical Direction Elefant Studios AG Lessingstrasse 15 CH-8002 Zürich +41 44 500 48 20 www.elefantstudios.ch ---------------------------------------
