-
Notifications
You must be signed in to change notification settings - Fork 3k
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- Select a note
- Press F2 or use context menu to enter Edit mode
- Press cursor keys to move note
Result: very erratic. Mostly nothing happens at all, but sometimes I see the pitch change dramatically (down to lowest possible pitch, C-1), sometimes I see leading space increased, and occasionally a crash (I don't have specific steps for that, though).
Supporting files, videos and screenshots
Screen.recording.2025-12-27.10.22.56.AM.webm
In which versions of MuseScore Studio is this issue present?
OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.0-253610331, revision: github-musescore-musescore-b37f7cc
Regression
Yes, this works in the latest released version and is broken in the nightly builds
Operating system
Debian 12
Additional context
Console output isn't very helpful. It does report edit mode was initiated.
Edit mode / keyboard nudge does appear to work normally for at least some elements - like articulations and time signatures. Key signatures don't work either, though (but do in 4.6.5). Clefs don't work in 4.7 or 4.6.5, and "Edit element" doesn't appear in the context menu so I guess that's by design.
Behavior seems independent of whether "snap to grid" is enabled.
I wonder if #29287 might involved here somehow, but it was was also ported to 4.6 which seems to work fine.
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