It's a pretty general plugin unfortunately (an extended image exporter that handles higher bit depths and the like). I need to open it in QC and play with the settings really (like the bit depth of a render in image, which isn't available as a published port :( )
My other problem is that I have a QC comp that has to run 24/7 on this box. I can quit + reload it and mess about so long as it's quick, but connecting it up to the debugger is probably not on the cards. Oh well, I'll have to live with doing it manually and writing NSLog() a lot. On to the next question then (I'll start a new email so as the subject matches) Thanks for the help! Chris On 20 May 2010 14:26, Christopher Wright <[email protected]> wrote: >> Is there a nice way to debug QC plugins? I.e. without loading them >> into QC, opening a composition, hooking the plugin up and trying to >> decipher the backtrace when it crashes.. > > > Since the plugin itself is a loadable bundle, it isn't standalone -- it > cannot be executed by itself (it needs a host process). > > It's possible to make a host app the loads QCPlugins (they're bundles, so > anything can load them), and do stuff with them. > > Is that what you had in mind? Or did you have another use-case? > > > -- > [ christopher wright ] > [email protected] > http://kineme.net/ > > _______________________________________________ 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]
