Re: Possible to package an AU with an app?
Re: Possible to package an AU with an app?
- Subject: Re: Possible to package an AU with an app?
- From: Marc Poirier <email@hidden>
- Date: Fri, 12 Sep 2003 12:06:38 -0500 (CDT)
On Fri, 12 Sep 2003, Glenn Olander wrote:
>
Marc Poirier wrote:
>
> Have you found that RegisterComponentFileRef returns noErr no matter what?
>
> I'm finding that in my experience. I mean, I tried registering completely
>
> ridiculous stuff, like FSRefs to audio files and zip files and stuff like
>
> that, and every time RegisterComponentFileRef says, "noErr, everything is
>
> a-okay honkey dorey." And I'm thinking, "Pffft, yeah whatever..." But
>
> it's a little concerning that there's no way to error check, then how can
>
> you rely on RegisterComponentFileRef?
>
>
That's very true. But, in practice I don't think that's a critical
>
problem because you can do your error handling when you try to find
>
the component.
I know, but that's actually why I'm playing around with it because I'm
trying to debug a component that, on one person's system, will not be
recognized by the Component Manager. By the time I get to
FindNextComponent, the Component Manager has already decided that it
doesn't like my component and doesn't report it's existance.
FindNextComponent doesn't give you any sort of error reporting, just a
"here's what I got for you" sort of response. I'm trying to figure out
how to debug what happens when Component Manager encounters my AU and then
says, "naaah, I don't like you." But maybe this is another issue and I
need to come back to this in another message, and maybe I'm just going
about investigating my problem in the totally wrong way (but I was just
hoping that RegisterComponentFileRef would help me)...
>
Regarding error checking, It's always made me nervous about how easy it
>
is for anyone with the Finder and a text editor to muck with a
>
bundle. How do you know a bundle is valid/intact?
Heh heh, I love the hackability of OS X! :) But I've thought about it
from that view point, too. Like recently I was working on an app that
relied on a certain other bundle having a certain bundle identifier, and I
was thinking, "well, but what if the user tampers with that and changes
it, should I have some sort of fallback?" But then I thought, whatever,
if someone does stuff like that, they have to expect that they might break
something. And if they are hacking like that, they probably know enough
to know how to revert whatever changes they made. Anyway, this doesn't
really answer your question I guess, but I was just thinking about it
recently too, and just sharing my thoughts...
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.