I don't know of anyone who's successfully had composition-relative paths work in an application yet (without managing path building themselves to some degree) -- I'm sure there's a way though, I just don't know it.
Okay my curiosity is piqued... Can you clarify what you mean by that a bit more?
Are you specifically referring to non QCView type apps?
Yep, this is exactly what I'm referring to. QCView is cheating in this context since it handles all the environment setup "automagically." When making a QCRenderer, there is something that needs to happen for compositionURL to be valid (i.e. not / ), but I'm not sure what it is (I don't spend enough time fighting with this to figure it out, but I'm hoping that someone else has.. *shrugs*) -- maybe it is handled automatically with QCRenderers too, and I've just missed the boat on Leopard?
Good point on distinguishing the use-cases though; this is only of interest when using QCRenderers, not QCViews. Thanks for pointing that out :)
-- [ christopher wright ] [EMAIL PROTECTED] http://kineme.net/ _______________________________________________ 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]
