Shift+left arrow key from single selecion before multimeasure rest leads to range selection up to end of score

• May 4, 2015 - 01:58
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

A standard way to select a range is to click one note or rest, hold down the Shift key, and use the right or left arrow key to extend the selection. (I'm all the more likely to do this because holding down Shift and clicking not exactly on a note head now leads to a multiple note selection, not a range selection—perhaps something I should file an additional bug report for? Never mind for now.)

However, in MuseScore 2, if the initial note or rest is just before a multimeasure rest, attempting to select to the left—that is, holding down Shift and hitting the left arrow—actually ends up selecting the entire score to the right.

Note that this does not apply if the initial note or rest is already selected as a range selection. To reproduce, you may wish to hit Escape a couple of times before clicking on the note or rest.

Comments

• Jun 14, 2015 - 15:27
Title Regression in 2.0—Shift+left arrow key selection starting before multimeasure rest leads to selection up to end of score ⇒ Regression in 2.0—Shift+left arrow key from single selecion before multimeasure rest leads to range selection up to end of score
Status (old) needs info ⇒ active

I believe the clarification I just added to the title should enable you to reproduce it—the note or rest before the mmrest should simply be clicked on, not Shift-clicked on.

Reply

• Jun 14, 2015 - 15:31
Status (old) active ⇒ needs info

I tried that, and it workll s fine for me in a current build with the example I used. Again, please, if you can reproduce this in a current build, we need a specific score and precise steps (precise in this context = tell me which note to click).

Reply

• Jun 14, 2015 - 15:59

Sorry for the delay—I wanted to check with the very latest nightly. In 6d09138, it still behaves the same way with any score, but the specific one I believe I uploaded before was this one: Untitled.mscz

Just to be very, very specific:
1. Open attached score.
2. With nothing selected, click once on the quarter rest in measure 2. There should not be a blue rectangle around it.
3. Hold down Shift and press the left arrow key, extending the selection to the note before it, one note toward the beginning of the score.
4. Expected result: the last two beats in measure 2 will now be selected in a range selection. Actual result: they are, but so is everything in the opposite direction up to the end of the score.

Reply

• Jun 14, 2015 - 16:04
Status (old) needs info ⇒ active

Thanks, reproduced. FWIW, everything else is not *actually* selected; the blue rectangle is just confused. Try pressing Delete...

Reply

• Jun 14, 2015 - 16:38
Title Regression in 2.0—Shift+left arrow key from single selecion before multimeasure rest leads to range selection up to end of score ⇒ Shift+left arrow key from single selecion before multimeasure rest leads to range selection up to end of score

Confirmed also.
For the record, it's not a "Regression in 2.0" (released on 2015, March 24).
I see the same behavior since more one year on a Nightly on 2014, May 19

Reply

• Jun 14, 2015 - 17:13

Ah, but that would be a nightly build of 2.0, wouldn't it? The issue definitely was not present in the 1.x branch, or at least not in its final release, 1.3. That's what I meant.

Reply

• Jun 14, 2015 - 19:22
Status (old) active ⇒ patch (ready to commit)

cadiz1: it is a subtle distinction in English. Regression *in* 2.0 means, something broken in 2.0 that worked in a previous release (eg, 1.3). Regression *from* 2.0 would mean, something that worked in 2.0 but no longer works. So, "regression in 2.0" and "regression from 1.3" mean the same thing.

In any case, it isn't necessary, or really particulatly useful, to include that information in the issue title. It's good information for the body of the issue of course. Maybe at most, "regression from 1.3" in parentheses at the *end* of the issue title if it isn't on the long side already. Thats my opinion anyhow. I like the first words of an issue title to summarize the basic problem area.

Oh, yeah, and this one is a very simple fix :-)

https://github.com/musescore/MuseScore/pull/2069

Reply