Hi! It's okay, it really is something that I also thought was kind of picky, but I meant it as something additional to what's already currently implemented. Because for me personally, I felt that if I wanted a multimeasure rest, I would first try selecting all the empty measures, and see if there was an option under Measure Properties to make it a multimeasure rest. And if the number of empty measures was too large, then just typing in the measure numbers as boundaries.
But obviously, if it's something that in the end is redundant, then it's not a great idea. I really appreciate your feedback, thank you for taking the time to reply! Sincerely, Joyce -- View this message in context: http://dev-list.musescore.org/GSOC-2016-Project-Idea-Multi-Measure-Rests-tp7579660p7579663.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
