musescore / musescore/MuseScore

Design in-app instructions for the "Find/go to" command bar

Open
#22,946 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request needs design
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Feature description

The "Find/go to" bar (Ctrl/Cmd + F) provides no hint on how to use it. Users must look up the command syntax in the handbook to see how it works.

We could provide a quick how-to reference in a collapsible "How to use" section or in a popup.

image
From the handbook:
  • To go to a numbered measure: enter the measure number (counting every measure, starting with 1, irrespective of pickup measures, section breaks or manual changes to measure number offsets).
  • To go to a numbered page: enter the page number using the format pXX (where XX is the page number).
  • To go to a numerical rehearsal mark: enter the number using the format rXX (where XX is the name of the rehearsal mark).
  • To go to a rehearsal mark starting with a letter: enter the name of the rehearsal mark (the search is case insensitive).
  • N.B.: It is best to avoid naming rehearsal marks with the single letters "R", "r", "P", "p", or one of these letters with an integer (e.g. "R1" or "p3"), as this can confuse the search algorithm.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing "Find/go to" command bar and the handbook syntax listed in the issue. Determine whether the reference belongs in a collapsible section or popup, and consider the listed measure, page, and rehearsal-mark cases covered when the instructions are available in the bar.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
design, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.