site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com If you are developing with XCode- and I think you should be - then debugging is quite easy. Once you have compiled and done the usual voodoo, you launch the host app, and attach the Debugger to it in XCode’s Debug menu. Logging and breaking in your code should work as if this was a stand-alone app. These steps can be achieved with a post-build script - see Post-actions in your build settings in the Scheme editor. Hope this helps, Rainer
On Sep 11, 2017, at 09:44, fnelson@clemuniversity.com wrote:
I'm having an issue while testing my plugin where the FXPlug seems to occasionally unregister itself. I copied my compiled fxplug .app to my Applications folder and run:
pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal.
I open Motion, create the motion effect and everything works perfectly in FCPX... for a while. Then it might be after a restart or just after a few hours, FCPX won't see it anymore. Has anyone else experienced this? Also, can anyone give me ideas for the best way to debug an FXPlug plugin? Thanks so much!!
Caroline _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/lists%40standke.com
This email sent to lists@standke.com
_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com