- question for the dev team:is there any information provided in the execution context that could inform a plug-in that its inside an iterator? the documentation doesn't indicate any, and if there would it allow state-saving patches to 'do the right thing' automatically.
It's possible to do this by using some unofficial API calls, but that's probably not recommended. It's not overly difficult though, mind you. Alternatively, you could have the patch track the times that it's executed at, and if subsequent executions have duplicate times, you're inside an iterator. I don't necessarily think that's a good solution, but it's one that would work without any hacks (it also requires applications to fill in valid timestamps when rendering).
As a general extension to this idea, I've run into a number of instances where graph hierarchy introspection would be wonderfully helpful; doing the Right Thing in GLSL patches is different if you're not in a GLSL patch; sometimes knowing what parent 3D patches (lighting, fog, trackball, among others) can help you do less work depending on what/how you're rendering. So having a way to find out if you're "inside" a given set of patches, and then finding that patch's (or patches') parameters would be helpful in those cases.
Is that too over-the-top? -- [ christopher wright ] [EMAIL PROTECTED] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
