Thanks for the quick replies! So he basically tricks Maya into dirtying his plug in the draw method? Nice. So in my example, I would query the value of a third dummy attribute- something lighter weight than an array like a float or int and use that to force the eval? Can do!
* > how about writing a node to compute your pointList and plug it to your locator that will only draw from * Absolutely the way to go, but I thought I would save time and test the idea in one node. But then nothing worked :) Additionally, I'm now fighting python just to call compute with * MFnTypedAttributes*. Two examples, slightly modified versions of Farsheed's skeleton code. The first one has MFnNumericAttribute as the output attribute and it calls the compute method as expected. The second one is bunk though and I cannot figure out why. Hmm. Take a look: nodeNumeric.py: http://pastebin.ubuntu.com/1030758/ Works a charm, compute gets called. nodeTyped.py http://pastebin.ubuntu.com/1030764/ Compute never gets called. Silently fails? Only changed the attr type to TypedAttr and kDoubleArray. Nada. Zilch. Zippo! Did I miss something obvious? Thanks. -shawn -- view archives: http://groups.google.com/group/python_inside_maya change your subscription settings: http://groups.google.com/group/python_inside_maya/subscribe
