Unchecking a staff in Measure Properties is not fully Undoable
@mathesoncalum is already working on this.
Since Oct 11, 2024.
Assessment
This issue has not been assessed yet.
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- Create a new file with at least two staves or (alternatively) open the attached file.
- Right-click a measure and then open Measure properties.
- Uncheck the first staff.
- Ok out and then Undo.
The measure remains hidden and this cannot be Undone. However, internally the code seems to think it is not hidden. You can see this by
- Reopen Measure properties. The Staff is showing checked even though the screen is showing it hidden.
I have marked it "UX/Interaction" but there potentially could be "File corruption."
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
Latest dev version
Regression
No.
Operating system
macOS 12.7.6
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
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·