Re: Meta Parameters
Re: Meta Parameters
- Subject: Re: Meta Parameters
- From: William Stewart <email@hidden>
- Date: Fri, 4 Apr 2008 11:32:57 -0700
On Apr 4, 2008, at 8:24 AM, P. Grütter wrote:
Hi Bill,
is it right that a meta parameter change just calls the listener for
all dependent parameters?
no - it will evaluate the parameters and send notifications if they
have changed. By describing what the dependent parameters are, it
allows this mechanisms to have a shorter search path.
Is it the same not to use meta parameters but call AUParameterSet()
for every single dependent parameter?
No - auval will fail your AU because you have incorrectly marked one
of your parameters. Also, the intention of this mechanism is that the
AU itself doesn't have to do this notification as its not setting a
parameter value, just responding to it being set on it.
Bill
Because I have to set all dependent parameters anyway, why not use
AUParameterSet() to notify the listener?
Thanks, Paul
Am 3. Apr 2008 um 21:00 Uhr schrieb William Stewart:
The interdependencies shouldn't really matter.
What is helpful is:
Button 1 - meta parameter
button 2, 3, 4 are dependents on this
Button 2 - meta parameter
button 1, 3, 4 are dependents on this
I don't think it should matter too much. If it does, then just
don't publish the dependent parameters (in which case the default
behaviour is that as you've changed one parameter any other
parameter could change)
Bill
On Apr 3, 2008, at 9:47 AM, Kevin Dixon wrote:
You might have to track this yourself some how. AFAIK, you cannot
define
the relationships between your parameters.
I think basically, if a parameter is defined as a Meta parameter,
it means
that auval will not fail if other parameters change when it does.
Hosts may use this information for their own devices, as to
determine if
they should refresh drawing of your AU, but I'm not exactly sure
on that.
-Kevin
Hi,
you can ignore my last post, I've solved it mostly. But I still
have
problems with the Meta Parameters.
In my case I have buttons that interact with each other, e. g.
switch
on button 1 switches off buttons 2, 3, and 4. But button 2
switches on
button 1 and switches off the buttons 3 & 4. So all of my buttons
are
both meta and dependent parameters. Is there any way to define
this? I
want the listener to know if this call is caused by the user or
because this parameter is a dependent one.
Thanks, Paul
_______________________________________________
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
_______________________________________________
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