As far as I'm aware you've gotten right that Environments might have their 
inputs published up and thus be available for setting as a virtual macro patch. 

The GLSL patch is of course a programming patch, to which the same rules apply 
, it seems also to OpenCL and Core Image and JS patches , namely, one can edit 
the .qtz that houses the virtual macro, but apart from publishing up inputs and 
publishing up outputs, a macro patches environment settings are provided by the 
virtual macro pretty much as a consumer patch, with the patch designer deciding 
what should be made available from the inputs housed within. 

We don't seem to have the facility to make the editable panes available from 
within the virtual macro as presented upon the Editor stage. 

The distinct difference here is between dragging and dropping say a pretty 
useful construct, design or utility composition onto the Editor stage, which 
will provide environmental access and on the other hand, dragging a virtual 
macro clip onto the stage and either you've got an input / output utility of 
some type - image filter, string formatter, whatever, or else you'll be getting 
a consumer patch that structurally contains all sorts of facilities , either 
they run automatically, or else they have inputs and sometimes outputs.

I can't speak for the viability of unregistered patches, but point is the more 
exotic, the less mainstream, the less likely it will work far outside of its 
real brief and bailiwick :-)

It's a pretty audacious and useful feature requests, but changing the scripting 
within such a macro, if it were made possible, could likely as not change and 
possibly damage such an composition.


Perhaps what is needed is for the object oriented patches to be capable of 
cloning themselves to be embedded be-spoked within the clone of their original 
and still intact virtual macro.

What about placing that virtual macro GLSL patch within an Environment as and 
when you want?

 _______________________________________________
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]

Reply via email to