So, we're pretty much ready to release 1.1, but... Ok, so I don't really like to rip on other people's code, there's definitely problems with some of my own code as well so can't really point fingers... however, lately, I've been thinking that the current implementation of logarithmic models is flawed.
Firstly it breaks backwards compat... if you open an old project made with 1.0 or earlier, and you have automation of a knob that is now logarithmic, the automation curve will be different. Secondly I'm starting to think things like logscale should be done on the UI level, not on the actual data models... the current way of doing things is likely to cause problems down the line. Instead of doing the logscale conversion on the model, I think it might be better for the model to just contain a hint whether it should be log/linear, and the knobs & automations could handle the logscale-representation on their end. Because the automations and widgets have to take logscales in account anyway, it'd be better for them to handle it entirely... it'd be a cleaner solution. So fixing this is likely to cause yet more delay to the release of 1.1 (which is already behind schedule by 4 months or so), but I think it'd be better in the long run because if we release 1.1 as is, it'll break backwards compat now, and then if we fix the logscale feature later it'll break backwards compat again. I might be able to work on this during the weekend... ------------------------------------------------------------------------------ _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
