Re: MultitapAU compiling as folder
Re: MultitapAU compiling as folder
- Subject: Re: MultitapAU compiling as folder
- From: Howard Moon <email@hidden>
- Date: Thu, 24 Feb 2005 13:00:01 -0800
I just do a GetInfo on the bundle, and paste my own custom icon onto
it. That lets each of my plug-ins have their own icon, instead of
relying on a specific host to claim "ownership" and show its icon (like
Cubase does for my vst components).
-Howard
On Feb 24, 2005, at 6:56 AM, Marc Poirier wrote:
It's going to continue to have a folder, just not open like a folder
or have an arrow next to it in Finder list view, until some app claims
to handle the component file type and provide an extension. In my
opinion, it's a bug in Mac OS X that still no system app does this. I
made one just because I found it annoying (see DFX fake app at
http://destroyfx.org/audiounits.html at the bottom).
Also: http://www.mat.ucsb.edu:8000/CoreAudio/10
Marc
On Feb 23, 2005, at 5:43 PM, Asli Binal wrote:
Hi all,
I've already read most of the replies to earlier posts about
multitapau sample compiling as a folder - I've tried all the
suggestions and still experiencing this issue.
Both the MultitapAU+View, and MultitapAU projects build successfully.
The version of Xcode is 1.5, CoreAudioSDK is 1.3.3...
I tried adding the GENERATE_PKGINFO_FILE to the active project
settings, yet I still get a MultitapAU.component folder...
any ideas?
Thanks,
AB
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden