Open Ash-86 opened 1 month ago
Until 4.4, performing this operation would only leave the first rest selected. When implementing the list selection, it was decided (for notes) to only keep the ones selected that existed before the duration change operation. Should this really be different for rests?
THat's a good point actually. I agree. I dont suppose the the issue with rests can be implemented without affecting note selection behaviour after a duration change (which obviously makes sense the way it is). can it? In that case should i close the issue?
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/eaf05b43-7643-409f-a9a5-0a2692fdd661
What is the latest version of MuseScore Studio where this issue is present?
4.4.1
Regression
No.
Operating system
windows 11
Additional context
...because of that, further note-value changes only affect those at the first beat of every bar. If, however, all rests ended up selected, further changes to duration change all rests.
This is very useful for people who like to subdivide the whole score for a grid-like experience.
currently that can be acconlipshed using several steps which can be a bit of a hassle.
Checklist