Open avvvvve opened 1 month ago
@oktophonie @mike-spa feel free to move out of 4.4.2 if this doesn't feel urgent or edit if any of this doesn't make sense!
@oktophonie @avvvvve I've spent a couple of hours looking into this. It all makes sense (and I've definitely thought about it before). The reason't I haven't done this yet is that it's quite a large job because (unlike dynamics, but like every other text-based element) expressions have never had any "reanchoring" property. In fact, "expressions" didn't even exist until I created them a couple of years ago: they used to be just styled staff text. The re-anchoring does work when the expression is attached to a dynamic simply because in that case the expression just follows what the dynamic does (it doesn't need to be able to find its own renanchoring points). Now that I have a clearer picture of this, I can confirm that it's surely doable, but also definitely not patch-releasable, so I'm moving this out of the 4.4.2 project.
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Expression text should have some of the same behaviors that dynamics have:
Supporting files, videos and screenshots
For no.3 above:
https://github.com/user-attachments/assets/9cb018d2-f260-4f5f-89ef-518de28f7927
What is the latest version of MuseScore Studio where this issue is present?
5.4
Regression
No.
Operating system
macOS 14.5
Additional context
No response
Checklist