"QC certainly puts a temptingly simple face on some extremely powerful (but very complicated) technologies :)"
Seems like a design ideal an entire company could be built on. :) Keith. ######## On Thursday, 10 February 2011 at 11:19 AM, Christopher Wright wrote: > One possible improvement: have the execution + UI on separate threads > somehow. This way at least if it's looping you have some chance of the stop > button actually doing what it should. It won't work in all cases, but might > possibly work in some? > > Separate threads would alleviate much of the problem -- you could save your > work, for example. But you _cannot_ arbitrarily terminate threads > (safely/cleanly). So an infinite loop means you'll have to ideally change > your work so that it's not doing that, save it, and then quit/relaunch the > app (so that the runaway thread goes away). A huge improvement no doubt, but > still a bit clunky. closing the document wouldn't clean up the thread, so > that's still a bit difficult to convey. > > (For the astute: yes, Safari warns you about run-away scripts. no, they don't > share that magic with anyone, unfortunately :(). > > QC certainly puts a temptingly simple face on some extremely powerful (but > very complicated) technologies :) > > -- > 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
