I wasn't aware such a bug existed. Should we have a bug report open on this (or do we already)?
As far as implementation prior to 1.1 release, I'm in agreement that its a bug worth waiting for however I'm also curious what the severity of this bug is: https://github.com/LMMS/lmms/issues/1198 Lukas just fixed this one: https://github.com/LMMS/lmms/issues/1065 Vesa just fixed this one: https://github.com/LMMS/lmms/issues/1238 First time commit grindhold just fixed this one: https://github.com/LMMS/lmms/pull/1243 (I staged it for stable-1.1 as well) This last week has been tremendously productive considering how busy everyone has been with school, etc. (not to mention the laundry list of changes that have come previously) Stable-1.1 is going to be quite a remarkable release! -Tres -Tres
------------------------------------------------------------------------------
_______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
