Quote:
Originally Posted by MixMonkey
Just have to tie the name (that the user deals with) to the index that (CSI uses)
Instead of the name that's used at the moment, I propose we use something like:
Code:
1Threshold
2Ratio
3Bypass
4Bypass
This will let users differentiate between identically named parameters. It might entail a bit of trial and error on their part to work out what controls what (I use Patchwork for this as it has a learn mode as well as a list of parameters- very handy plugin )
It means that they'll need to type an alias everytime, but they're probably already doing this anyway (I know I am)
|
Don't forget to start at 0
Maybe some parse magic where the entry in the FX params column and the dropdown looks something like "0 - Threshold", but the code logic places "Threshold" in the cell -- with the number stored conveniently somewhere out of site
Bonus prize if they select the mapped cell and the correct cell in the FX list gets selected too (or something like that) to indicate what's what
Also, if you run of things to do
, you could add support for an alias for the FX name itself, this will be used for the FXMenu Zone concept we've been discussing...
All of this is already coded at this end, it was almost trivial