hell yea!
and also maybe a similar solution to when you want to move all that you've done
into another macro patch (such as render in image, trackball, lighting, fog
etc). AFAIK with standard macro patches you can just select a bunch of patches
and click on make macro, and it puts them in a macro. But with the above
mentioned patches you can't do that, you have to cut and paste, which can be a
major nuisance (if not for the very reason vade just mentioned).
Studio 107. 7 Westgate St. London E8 3RL
mob: +44 7958 783 832
tel: +44 20 8123 9986
fax: +44 20 8986 5496
work: www.msavisuals.com
play: www.memo.tv
On 28 Jul 2010, at 19:03, vade wrote:
> This gets infuriating after a while.
>
> Make a few patches within a macro within a macro within a macro (ha), like
> iterator, render in image etc. Publish a few outputs to the parent patches
> and up through your macro 'graph' to the top most patch. Within one of the
> sub macros other than parent, decide you want to encapsulate something into a
> new macro (say for organizational purposes), and all of a sudden your
> published ports are no longer published, forcing you to re-publish them
> tediously. This has to be a bug right? I can feel my sanity wither away. :)
>
> I have some suggestions regarding publishing, etc.
>
> When you control click/right click on a patch and select "Publish
> inputs" or "Publish Outputs", can we have a that check next to the items be
> triggerable for more than one?
> ie: select "Publish Inputs", get a contextual menu of more than
> one item. Be able to click on multiple items to enable the checkbox and thus
> publish all of them from within the one menu. This would save enourmous
> amounts of time, and also give the user a choice in what to publish and not,
> unlike the Kineme work around which, iirc, publishes all input ports.
>
> Add an additional menu option underneath Publish Inputs / Outputs,
> which would be "Propagate all published inputs to top level patch" (as well
> as outputs), similar to Kinemes addition. For those of us who have to work
> without Kineme for various reasons, its a real loss, and ought to be within
> the QC Editor Proper.
>
> Community thoughts on these ideas?
> _______________________________________________
> 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/memo%40memo.tv
>
> This email sent to m...@memo.tv
_______________________________________________
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 arch...@mail-archive.com
