musescore / musescore/MuseScore

Provide feedback when enabling/disabling "Toggle multibar rests"

Open
#34,020 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

When "Toggle multibar rests" is toggled with a keyboard shortcut, there should be a visual feedback, such as a toast popup that says "Multibar rests ON", or perhaps an indicator somewhere.

Problem to be solved

I had no idea this feature even existed. I added some bars, and multibar rests were created, with no evident way to split them. It was frustrating to fumble around and search around to eventually discover that I had probably accidentally pressed Shift-Cmd-M at some point and enabled it.

Some feedback at the time I did it would have avoided this problem.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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 locating the Toggle multibar rests action and its keyboard-shortcut handling in MuseScore. Check how other toggles provide visual feedback, then implement feedback that clearly reports whether multibar rests are enabled or disabled and verify it by toggling the shortcut.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.