site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi, Ben, HTH, - Paul On Oct 15, 2007, at 12:27 PM, Benjamin Kent wrote: Hi Thanks _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... -userHasCancelled means that you should abort rendering, because some user activity has invalidated your render. In other words, the user is dragging a slider, so the parameters have changed since you started rendering. We will be calling you to render again with the new parameter values, or new time, or whatever else has changed. Each user action triggers a new render; checking for - userHasCancelled lets you abort an invalidated render early so you can move on to the next one. If you want to temporarily disable rendering entirely, so you can adjust a bunch of parameters without any lag, you can hit caps lock in FCP. Motion doesn't have the caps lock mechanism, but they render effects on a secondary thread, so the UI stays responsive. Looking at the Slow_SolidColor example, it would appear that even when you hit escape and the plug-in catches the interrupt with a call to userHasCancelled, the plug-in just gets asked to render again anyway - i.e. the cancelling doesn't really work. Is hitting escape not the correct way to interrupt or is this a bug? Ben _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider% 40apple.com This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com