Thanks for your help, Toby. A few questions are left: > I > propose to add a boolean property to AutomatableModel which indicates > whether the model represents a linear or logarithmic value - or even > more generic, an enumeration which could include further progression > formulas in the future. So you mean to bind the property to a model (instead of a connection, like I proposed)? This would restrict the user to not use two scale types to control one model (i.e. one logarithmic, one linear). Does anyone think this restriction is too restrictive?
Anyways, if I bind this property to the model... How to activate it then? Self activation for effects? Then imagine you add an effect, how should LMMS know that the scale should be logarithmic? I think LMMS can only guess it for some cases. So I think it is compulsory to add an option in the right click menu to let the user choose the scale type (with the assumption that the user is more clever than the computer ;) )? > For the actual implementation, you only need to extend > AutomatableModel::setAutomatedValue() and > AutomatableModel::controllerValue(). Ok, I guess the first is for automation tracks and the second is to receive a value from the controller for my model (e.g. a knob receives a new value), correct? ------------------------------------------------------------------------------ Androi apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
