I'm trying to create a simple patch that mimics a push button. Depending on the state of the button, the color of the rendered sphere changes. I'm trying to wrap this in a macro/clip where the inputs would be the origin and size of the button and the output would be the current button state, but QC isn't letting me create such a macro-- or rather it is, but then it seems to be changing its mind later and removing the output ports (which I think is a bug, where the intended behavior is to prevent such a macro outright).
The only reference to a similar situation I can find in the list archive is this: http://lists.apple.com/archives/quartzcomposer-dev/2005/Apr/msg00029.html Is this still a limitation of QC, or is there a way around this? The reason given in the old post is an order of execution argument, but I would think this could be easily circumvented by first executing then rendering. Do I basically have to keep the full UI at the top level of the patch? Thanks for any help. _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
