Thanks for taking my comment in the spirit in which it was meant!
If it were just about having an additional way of creating them, I wouldn't
be concerned. But right now, multimeasure rests are an all-or-nothing
thing internally, and this assumption is spread throughout the code. We
have had a number of bugs involving multimeasures rests and changing the
implementation to allow some rests to be combined but others not (other
than the current method where you can set a measure to explicitly break
them) would probably be a fairly risky change.
But now that I think about it, I can imagine a new option you could enable
along with the multimeasure rest mode, and when this option is set, all
measures would be treated as if they had "break multimeasure rest" set by
default. Then a new command to combine rests into a multimeasure rest
could be created; this would just explicitly set a new measure property
"don't break multimeasure rests" that would make these measures work
"normally". I think something like this could be implemented without major
changes. In fact, it's probably not a big enough change to make a good
GSoC project :-), but it is possible something like this could be combined
with other related ideas.
Marc
On Mon, Mar 14, 2016 at 8:31 PM Yomj <[email protected]> wrote:
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
