> Of course an option would be the best solution but for the time being, > hardcoding the property for some models (like freq knobs) is less > work. However feel free to implement an according context menu action. > A hardcoded property still could be used as a hint for the default > setting for various models.
Ok, almost all effects that I have seem to be LADSPA, so they should be all easy-auto-detectable. For the question of backwards compatibility: I think this *forces* us to save the scale type (linear or log). Why? Imagine you read a file with a logscale model. Even if it was saved with a "new" (i.e. logscale detecting) lmms version, it might have been created with an old version, so the user might expect linear behaviour. ------------------------------------------------------------------------------ Android 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
