Re: Meta Parameters
Re: Meta Parameters
- Subject: Re: Meta Parameters
- From: William Stewart <email@hidden>
- Date: Thu, 3 Apr 2008 12:00:15 -0700
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