Re: Filing of User Presets - files vs. builtin
Re: Filing of User Presets - files vs. builtin
- Subject: Re: Filing of User Presets - files vs. builtin
- From: Bill Stewart <email@hidden>
- Date: Fri, 25 Oct 2002 12:03:39 -0700
on 24/10/02 6:50 PM, Robert Grant wrote:
>
On Thursday, October 24, 2002, at 02:15 PM, Bill Stewart wrote:
>
>
>
>
> I'm still digesting the rest of the comments and trying to understand
>
> if
>
> there has been any consensus reached on this matter - if anyone feels
>
> like
>
> writing a summary of the ideas presented that would help an overworked
>
> designer here understand:)
>
>
>
> Bill
>
>
>
I'll try to take this on as I raised the issue in the first place.
>
>
First a description of the background to the problem.
>
>
AUs can ship with a small number of conveniently embedded factory
>
presets. User
>
can extend this set of presets by saving custom configurations as a
>
user preset
>
and setting the AU to use the preset by passing in the data and setting
>
the preset
>
number to -1.
Small nit-pick:) - you don't need to explicitly set the preset - when the
class info property is set it will do this for you, including the setting of
the name if found, within the class info
Bill
--
mailto:email@hidden
tel: +1 408 974 4056
__________________________________________________________________________
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
__________________________________________________________________________
_______________________________________________
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.