musescore / musescore/MuseScore

Crash when interacting with time signature properties after selecting via keyboard

Open
#22,085 5 comments 0 reactions 5 assignees View on GitHub

@zacjansheski is already working on this.

Since Apr 3, 2024.

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

Description

Issue type

Crash

Steps to reproduce
  1. Open a score
  2. Press the "right" key on the keyboard
  3. Press "Alt" + "Left" to select the Time Siganture
  4. In the Properties Panel click on "time signature properties"
  5. See no beaming options
  6. Click in the empty space in the 'Beam groups' box
  7. Crash

The crash should be fixed, and the beaming preview windows should appear.

MuseScore Version

OS: macOS 14.1, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433


Original issue

Issue type

UI bug (incorrect info or interface appearance)

Bug description

If you select the time signature using the keyboard and open "Time signature properties...", no beaming options are displayed.
The interface even freezes when you click on OK.

image

Steps to reproduce
  1. Open a score
  2. Press the "right" key on the keyboard
  3. Press "Alt" + "Left" to select the Time Siganture
  4. In the Properties Panel click on "time signature properties"
  5. See no beaming options
Screenshots/Screen recordings

No response

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

I don't know

Operating system

Windows 11

Additional context

If you have a Keyboard Shortcut for "time siganture properties" this also does not work.
If you click the time signature with the mouse all things are right.

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.