site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Same setup as Brian. - Stoney On Aug 31, 2009, at 3:35 PM, Brian Gardner wrote: This happens to me even when running the example FxPlug code, and with no project open in FCP or Motion. So, either it's because of which versions I use, or because of some extension I have that effects both FCP 7 & Motion 4. Everything works fine... I just can not debug. The Xcode debugger won't attach to FCP 7 or Motion 4. Does anyone else have this problem? -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ _______________________________________________ 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... I have recently debugged plugins in Motion 4, and didn't have a problem doing so. I haven't tried FCP 7 yet. Since I've upgraded EVERYTHING (to Mac OS X 10.6, Xcode 3.2, FxPlug SDK 1.2.4, FCP 7, & Motion 4) and deleted all the plugins I could find, I'm stumped. I took me a while to discover this problem, because I haven't needed to debug anything for a while. All my FxPlugs are running fine in FCP & Motion. -- Brian This email sent to site_archiver@lists.apple.com