I've seen no major issues with this personally. I don't see why it would be a problem unless you are being careless with doing things in excecuteAtTime that re-draw the window or use non thread safe calls, which *might* cause threading problems should your plugin's host (whatever app is calling the QTZ you plugin is being used in) calls excecuteAtTime from a background thread (like say, CVDisplayLink, which lots of QC app examples use).
But no explicit reason it should not work to my knowledge. On Apr 26, 2010, at 11:34 PM, Rick Mann wrote: > I have a need to display some auxiliary information from my plugin, that > doesn't end up rendered to the destination. Is it acceptable to instantiate a > window and use bindings (or update views in the execute method) to display > this information? Or is that a big no-no? > > TIA, > Rick > > _______________________________________________ > 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/doktorp%40mac.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]
