Hi,

I've got a updating data feeding in to a classic particle shape. Particle 
shape changes in response (well, under certain circumstances, hence the 
question...).

When does it update in response? Whenever a draw event happens. Nice, just 
what we like.

Sometimes, we also like to twiddle nobs on incoming data, and see the 
result of that in the viewport without needing to 'nudge' it for a 
re-draw/fresh/update (nudge, as in wake it up with some flavour of mousing 
[or, a port state change, whatever]).

... I'm thinking of classic scenario where you tweak, say, rgbPP arrayMap 
ramps on classic particles (ie, no internal ramps like nParticles), and you 
don't get to see the fruits of your tweaking labors until you nudge the 
viewport. Yay (so, yeah, pipe something out of the ramp to a viewport vis 
dep thing to pull draws upon tweaks..., but for illustrative purposes, 
think of the default behaviour).

Now to the point, my incoming data WILL update the particles (read: elicit 
a draw), but only if the particleShape under question has been loaded in to 
the AE last. And i mean last. If i select another particleShape, and load 
it in to the AE, my original one driven by the data will now no longer be 
responsive to the incoming data tweaks (until viewport nudge/draw). 
Incoming data drives particleShape.inputGeometry. When its active, the AE 
need not have the particle tab displayed, or listed (though, even if it 
isnt showing, who knows what stays in its 'relateds' stack?).

So some sort of control or callback that is watching that particleShape 
attrs and triggering a redraw. I want that thing so i can do it myself 
(well, maybe not if its purely UI [which it seemingly will be]). I know i 
should paw over the AE particle template and go figure, but i was wondering 
if any of you fine folk had thoughts on the mater, for the particulars 
here, and perhaps any general comments on shape refreshes. And if you're 
feeling chatty, viewport 2.0.. i'm seeing incomplete support for particles 
atm (but glad-as to have them there finally!). Anyone getting busy with 
setAffectsAppearance()? I've been chucking some forced M3dView.refresh() 
around, which makes me a touch nervous.


Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to python_inside_maya+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/7eb26568-029e-4df3-920f-ffc3759be757%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to