That's an interesting idea. You should definitely file a feature
request ;-)
.xX
On Mar 14, 2008, at 12:22 PM, vade <[EMAIL PROTECTED]> wrote:
I really wish there was a checkbox somewhere to force computation
for a selected patch/object.
This would ease debugging greatly.
QC being able to optimize by only computing 'upstream' patches if
the downstream consumer is active is great for when the app is
running, but it does indeed make debugging a bit of a pain.
It would be nice to be able to select the furthest downstream patch
and 'force' it and its upstream patches to execute for debugging
purposes.
Is there any way around this besides patching a dummy consumer?
Sorry, do not mean to derail an interesting thread, i just often
find myself doing exactly that and sighing a bit more to myself
every time.
... like now :) To see your composition graph's peak speed, try
attaching the output to something that does next to no work, but is
a red patch. For example, attach the output image to the enable
input of an empty Iterator patch set to 0 iterations -- this means
the iterator does essentially no work, but the rest of the graph
gets evaluated anyway. This will tell you how fast QC can process
your graph without any graphical output overhead. By disabling the
only output, it causes QC to stop executing _any_ of the patches,
which probably isn't what 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/asabatelli%40apple.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]
