Re: AUGraphInitialize in audio thread
Re: AUGraphInitialize in audio thread
- Subject: Re: AUGraphInitialize in audio thread
- From: "Angus F. Hewlett" <email@hidden>
- Date: Thu, 10 Apr 2003 12:31:58 +0100
At 02:30 PM 4/9/2003 -0700, Brian Willoughby wrote:
>
Considering your needs - to alert the user about insufficient licensing -
>
perhaps CoreAudio should allow for an exception to be raised, or add a
unique
>
return code to indicate licensing restrictions. It would be up to the
host app
>
to display the text of the exception, or to interpret the return code.
>
>
It's a very common and powerful design principle to create code units which
>
have no UI. This technique allows them to be used in many more ways than
>
initially predicted. Breaking the paradigm by popping up alert panels is
>
probably something that will restrict the flexibility of AudioUnits.
I must say, I have some reservations about this. Specifically, what other
classes of functionality besides UI might break or be unsafe in these other
uses? Or is it -only- UI that's affected?
Also, is this restricted to Initialize(), or does it apply to constructors
as well?
Finally, with regard to error messages, how about a Property for "last
error message". So, whenever the plug returns an error, it can set the
contents of a text buffer (or even a more detailed structure) internally,
which the host can receive via a GetProperty() call.
Regards,
Angus.
=======================================================
Angus F. Hewlett, Technical Director
FXpansion Audio UK Ltd -
http://www.fxpansion.com
=======================================================
_______________________________________________
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.