Find a numerical rehearsal mark using Ctrl-F

• Apr 8, 2016 - 11:09
Reported version
2.2
Type
Graphical (UI)
Severity
S5 - Suggestion
Status
closed
Project

MuseScore can create rehearsal marks based on letters as well as numbers.

However, using the Find function (Ctrl-F) will not retrieve any numerical rehearsal marks.It searches for the corresponding bar number instead and quits.

So the feature request is: ability to search for a (numerical) rehearsal mark with the Find function (Ctrl -F).

A possible solution could be to use a "r" prefix in the Find text field to allow searching for any type of mark.

Cheers,

Dave


Comments

Status (old) active patch (code needs review)

While at it I disallowd measure number 0 to be searched for (doesn't make any sense) and allowed negative pages number to be searched for (these are possible)

I wonder whether this could get extended to allow searching for measure numbers as shown in score, i.e. take pickup measures, manual measure number offsets and section breaks into account?
This has been requested recently. Maybe with a '#' as the prefix to denote that you want to go to a 'logical' measure

Another possible extension would be to go to a certain section, e.g. entering "S3" would take you to the first measure of the 3rd section.
Mabye "S3#4" to get you to the 4th 'logical' measure (i.e. not counting a prickup measure) of that section.

Status (old) patch (code needs review) fixed

Fixed in branch master, commit 76f5bbf261

fix #105256: allow searching for numerical rehearsal marks

by prefixing with 'r'. While at it disallow measure number 0 (which by
definition doesn't exist anyway) and allow negative page numbers (which
are possible, via page number offset).

Fixed in branch 2.0.4, commit a3e89b0c20

fix #105256: allow searching for numerical rehearsal marks

by prefixing with 'r'. While at it disallow measure number 0 (which by
definition doesn't exist anyway) and allow negative page numbers (which
are possible, via page number offset).

yes
R is further down the alphabet and as such less likely to be use as a rehearsal mark itself, and also it is pretty close to P (shortcut for page) and S (for section, something I've been contemplating to implement)

Why does it matter if M might be used for a rehearsal mark? Only numbers can be searched for. And on my keyboard, M is actually closer to P than R is.

In my alphabet R is closer to P than M is.
And my idea to extend the search was to use p (page), r (numerical rehersal mark), # (relative measure number, relative to section and not counting pickup measures), s (section)

Hmm. I don't see any value at all to alphabetical proximity—unless it's actually consecutive letters, letters being sort of near each other might as well be random.

"...numerical rehearsal mark..." Not any letter. So what does it matter that R is less likely than M to be a rehearsal mark itself?

I get that "MM1" to find rehearsal mark "M1" would be confusing, but there's no way to find rehearsal mark "M1," right? At least, "RM1" doesn't do it. Or is that something that you're planning on?

My issue is that M is already for rehearsal Mark—see the default shortcut under Add > Text—and I'd hate to have to remember which letter is associated with the rehearsal mark in which context.

the M as a shortcut for rehersal mark is a moving target, users can cange it.
Searching for "M1" currently works (Ctrl+F, M1), but won't after your proposed change.

This is odd. In 2.0.3, "M1" doesn't work. In the nightlies, "RM1" doesn't work—but "M1" does. Shouldn't the prefix letter be required?