site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=IV2xlaAexkit3AsAxHrdCODrk0ClHxRYMp8yANqRLyE=; b=m4CcK5LiMbekHO+0S7IM909zS3i9nCJT7ChVNAqLCAAaVx/z2NmTDDY8u2lzoognIF gsRQxL6tVCjk/70dGgiy2biHs6I2R9c4Hcc72RjM3P+b1R5pTy7ssVGXQh/bThlhVk8s 9vaZLGAS0r53VIuRAgqrCVXKn/FANVxgjSBwQ= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ronZQp0yuUhUaf56j4898Ivr79RXk2W8Vdcr4pkY1CcQaPSqeDKAzZLX5ji9R1q4k4 vQ8+tYDVMh9eZy4FODBG2/KiSmlgHGucKjkh3MX1sXFF0JEWPaQ226OTubyTl5mg11wx 846S/y36NuLFNrgkhA6torJWDCcB27Brz955k= Hey George, This can be confusing, but a bundle really is just a folder, but the OS recognizes it as such and doesn't allow you to explore the contents in finder. if you right click any bundle (or app for that matter) you can select "Show Contents" and explore it as a folder. FxPlug files just don't have this feature built into the OS so Finder isn't smart enough to pretend it is not a folder. Make sure you've changed the UUID's from the example project (make sure to only change the ones that are different, 2 of them are should be the same - this tripped me up) and then put the .fxplug "folder" into /Library/Plug-Ins/FxPlug , relaunch final cut and you should see your plug in. To avoid UUID problems, just do this with one of the example projects to get it to show up in FCP, then try it with your own project. This will cut down on possible causes of error. If FCE isn't loading it still then there are other issues. On Fri, Oct 10, 2008 at 9:45 AM, George King <gkbox@arboreality.net> wrote:

Hi List,

I'm working on my first FxPlug and I am having a recurring problem. If I create a new FxPlug filter and build the default project, I get a folder called FxPlugTest.fxplug, rather than a bundle. This will not load in FCE. I was able to fix this by changing the wrapper extension to 'fxplug.bundle' under Target Info -> Build -> Packaging. However, after making some changes to my project (adding an application target, fussing around with the filter target's name, and some other things that should have been preceded by a snapshot), Xcode started building a folder with the fxplug.bundle extension. Moreover, When I created a brand new project to try to backtrack, the trick stopped working. Obviously I'm missing something, but it's hard to tell because all of the developer examples also build folders instead of plugins.

Any insight would be greatly appreciated. Thanks!

George _______________________________________________ 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/backsmith%40gmail.com

This email sent to backsmith@gmail.com

-- - Jim www.INTelegance.net _______________________________________________ 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... This email sent to site_archiver@lists.apple.com