Re: Private Parameters
Re: Private Parameters
- Subject: Re: Private Parameters
- From: Glenn Olander <email@hidden>
- Date: Tue, 15 Jul 2003 14:34:00 -0700
We might as well let everyone know we're talking about my
private parts here :-).
I can live with that, but it seems like a narrow definition
of parameter, especially since only #3 will apply to the
majority of plugins. (can anyone seriously see a generic UI
for any major plugins which have been released in the past
year?) Alternatively, we could add a flag to
parameter info that says whether a parameter is automatable
or not. That would seem like a useful thing to have in the
long run.
In any case, when you say "don't publish", does that simply mean
"don't include the id in response to a parameter list query"?
- Glenn
Bill Stewart wrote:
The intention of the published parameter information is to allow a host app to
(1) Build Generic UI
(2) determine which Params a host should listen to changes
(3) determine which parms can be automated (including ramped)
_______________________________________________
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.