musescore / musescore/MuseScore

Crash when a custom shortcut is used to open Staff/Part Properties and change instrument

Open
#28,531 3 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

accessibility crash os: windows P1
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Description with steps to reproduce

This crash is likely to effect screen readers using keyboard instead of right click mainly, so is also an accessibility issue.

STEPS:

  1. Go to Edit/Preferences Shortcut, search for properties and define a shortcut for Staff/Part Properties.
  2. Move focus to any note of a score (may need to have two staves or more).
  3. Press your assigned shortcut to open the Staff/Part Properties dialog box.
  4. Tab down to Replace Instrument and press enter.
  5. Select a new instrument and Tab to Ok and press enter.
  6. MuseScore crashes and closes.
  7. Expected Behaviour: Returns to Properties dialog box with new instrument added.

Is this related to having had focus on a single note rather than range selection when the dialog was launched?

Supporting files, videos and screenshots

N/A

What is the latest version of MuseScore Studio where this issue is present?

4.5.2

Regression

I was unable to check

Operating system

Windows 11 with NVDA

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.