Fix #33520: Allow unhidden instruments in part scores#33563
Fix #33520: Allow unhidden instruments in part scores#33563officialasishkumar wants to merge 1 commit into
Conversation
Keep master-part rows enabled when the part does not yet exist in the current part score so toggling visibility can create and show the instrument. Share the enabled-state rule between initial model setup and score-change refresh to avoid the inconsistent state that previously corrected itself only after another edit. Resolves: musescore#33520
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR refactors 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Resolves: #33520
Part-score Layout panel rows for instruments that do not yet exist in the current part score were initialized disabled, so the visibility control could not create and show them until another score change refreshed the row state. This keeps nonexistent master-part rows enabled and reuses the same enabled-state rule during score-change refresh, while existing rows still respect enabled shared parts.
Validation:
git diff --checkcmake -P /tmp/MuseScore/muse/buildscripts/ci/checkcodestyle/checkcodestyle.cmake src/instrumentsscene/qml/MuseScore/InstrumentsScene/internalI signed the CLA
The title of the PR describes the problem it addresses
Each commit's message describes its purpose and effects, and references the issue it resolves
If changes are extensive, there is a sequence of easily reviewable commits
The code in the PR follows the coding rules
There are no unnecessary changes
The code compiles and runs on my machine, preferably after each commit individually
I created a unit test or vtest to verify the changes I made (if applicable)