Ok, I have to admit I'm confused about "copied macros are clones". This is what happens with copy and paste already, no? Do you mean that Virtual Patches should all be distinct and editable in each qtz without changing the original virtual patch?
I would like to see the group of patches pull from the patch list "already exploded" (to avoid the lame limitation of not being able to have environment patches exposed) and all linked together, perhaps with some kind of outline around them (like when you select a group of patches, but a different color so that one knows it's a "patch group"). When you go to edit a patch in that chain, you would get a prompt to change either globally, add a new version of the patch globally through a save as, or simply change it locally in just that qtz. It seems like that is the most straightforward way BTW, I frequently use the old Composition Tool app (somewhere on Kineme, if you poke around long enough) to pull virtual macros back into the composition, where they can easily be edited without changing the original Virtual Patch. The Composition Tool pulls the original qtz, and places it where the Virtual Macro was. -George Toledo On Thu, Apr 29, 2010 at 10:27 AM, lists @ tobyz <[email protected]> wrote: > > On 29 Apr 2010, at 11:36, Adrian Ward wrote: > > > I see the copies-are-virtual-macros-by-default idea as being very useful > > > Finally, it would be nice to have an option whereby some virtual macros > are _never_ stored in a separate .qtz file in a library somewhere, and > _only_ in the original qtz. > > There is an elegant way through this I think. Leave virtual macros as they > are. Bring in an independent new feature scoped within compositions > themselves, where copied macros are clones. No conflict between these two > worlds, and the existing 'save flattened' (or whatever its called) option > could be used to unroll the instance'd 10.7 .qtz file. > > > And instead of a pony, can I have a lorikeet instead? > > No. I asked first =] > > > Ade. > > Toby _______________________________________________ > 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]
