Re: dynamically add / remove parameter
Re: dynamically add / remove parameter
- Subject: Re: dynamically add / remove parameter
- From: Stefan Kirch <email@hidden>
- Date: Tue, 18 Aug 2009 11:56:01 +0200
On 18.08.2009, at 01:21, William Stewart wrote:
My workaround consists of defining the dynamic parameters as
generic parameters (eg Custom1, Custom2 etc) and simply suppling a
0..1 range. In the UI I map the values appropriately for user
feedback and if the host supports value<>strings then I can supply
something more meaningful in automation editors as well. Also, if
the user has recorded automation data at least it will be in the
correct range even when the changes happen.
Yes, this is a common approach
Ok. Thanks for all the replies.
In my case i have a synth where the user can build his own modules
with any number of parameters. He can simply drag and drop custom
controls to a module and assign them to a parameter of this module.
Something like a cheap Reaktor clone. :-)
If i take Stephen's workaround does that imply that i have to create a
pool of "hidden" generic parameters and if the user needs a new
control i take the next unused parameter out of this pool and assign
it to the new control? Something like this? And then call
PropertyChanged to tell the host that the parameter might have changed?
stiwi
_______________________________________________
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