> 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. :)

known bug: <rdar://problem/5905075>  (and oldie from the looks of it).

> 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.

publish-to-root functionality is <rdar://problem/5147904> (even older than the 
above!)

Note that suggestions on-list are not the same a feature requests at 
http://bugreporter.apple.com -- please remember to file things there once you 
feel the idea is sufficiently discussed/refined.

This is a topic that has some already-known radars, but getting a really 
refined set of what needs to happen would be a great thing to have discussed 
some for a future version of QC.  Both of these radars were also filed 
internally, so no one outside has bothered to do so from the looks of it 
(neither have and significant duplicates from external users).

PS: In kinemecore you can do "publish all inputs" and then hit esc to _not_ 
publish a given input when the publish name editor pops up for that port.  It's 
kludgy, but the best I could do without really breaking stuff :)

--
Christopher Wright
christopher_wri...@apple.com



 _______________________________________________
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

Reply via email to