> Remember the KISS principle... and as corollary, Murphy's law. The
simpler we keep things, the less potential there is for things to go
horribly wrong...
Yes, that's why I hinted that not being the one coding makes my UI requests
fairly moot. From a composer's perspective, I never want discriminatory
automation areas, and I certainly don't want more tracks (the number of
average tracks per project is already a problem in my compositions).
Wishful thinking, but I'd vote for a design that doesn't introduce more
tracks. Even if the existing tempo automation track locks itself from
receiving non - automation drags, from my naive users' world, I would
advocate for a solution that keeps what we already have.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
