If you (by which I mean I) accidently put 654645 into the iterations input or divide by zero in a math patch or something equally stupid QC3 goes to beach-ball purgatory. Is there a way to kill just certain processes to kill the viewer window (ie not Force Quit QC3 or wait an hour in hopes) to allow you to save files fix idiot input etc? Just asking cause it'd be a shame not to know if there is.
the viewer window _is_ the editor window process (they're the same app, and the same thread), so there's nothing you can do. (Internally, there's some kind of execution abort flag, but I have no idea if it's honored, or how to swizzle it in the event of an emergency).
If you have kinemeCore installed (recommended on Leopard, use at your own risk on Snow Leopard), you can trigger its safety net feature by firing up terminal, and then running "killall -SIGSEGV Quartz\ Composer" -- that should trigger an emergency save. (Note that doing that will save the compositions to your desktop, and then return QC to its beachballed state -- if it's not actually beachballing, it'll return you to a working editor, which can be kinda neat (though it'll only do it once -- after that, the safety net's disabled to prevent infinite loops).
-- [ christopher wright ] [email protected] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
