...or in any scenario where there are multiple transforms going on (thought that info can be inserted into the javascript patch). It's also sort of tricky if you're mixing renderer types.
It would be great to have an appropriate fix for this where QC doesn't have to be locked into the driving the current layer system. -George Toledo On Thu, Sep 2, 2010 at 3:42 PM, Christopher Wright < [email protected]> wrote: > > My favorite solution to this is something Toby Spark posted a while back. > Make a structure and mark the positions off that you want in XYZ and attach > them to images so you structure contains all the metadata, and whatever it > is you want to draw. You can then do a structure sort on "Z" before sending > to the iterator and that does a kind of 'poor mans' depth sorting'. It works > very well. > > This struggles in a trackball setup like this though -- without having > access to the transformations applied, it's difficult to properly sort based > on distance from the viewer. > > (When trackballs aren't used, your/Toby's proposed solution is pretty > good) > > -- > Christopher Wright > [email protected] > > > > _______________________________________________ > 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/gtoledo3%40gmail.com > > This email sent to [email protected] >
_______________________________________________ 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]
