You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine that a user wants to add a chord note to a trill cue note. What is he doing:
Enter a chord of two (or more) notes
Add a trill line to the entered chord
Enable the cue note visibility in the trill Properties
Click on the displayed trill cue note
Press the key combination Shift + [chord key from A to G]
The trill cue note will move up an uncountable number of ledger lines. Obviously, this should not be the case.
Expected behaviour
In general, the trill cue note should have been initially displayed as a chord, and then the user would not have to resort to this kind of manipulation. As a result, there is a contradiction between what is written and what sounding:
Supporting files, videos and screenshots
Video_250126005254.mp4
What is the latest version of MuseScore Studio where this issue is present?
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Imagine that a user wants to add a chord note to a trill cue note. What is he doing:
The trill cue note will move up an uncountable number of ledger lines. Obviously, this should not be the case.
Expected behaviour
In general, the trill cue note should have been initially displayed as a chord, and then the user would not have to resort to this kind of manipulation. As a result, there is a contradiction between what is written and what sounding:
Supporting files, videos and screenshots
Video_250126005254.mp4
What is the latest version of MuseScore Studio where this issue is present?
4.5.0 250250300, revision: 3255273
Regression
No.
Operating system
Windows 11
Additional context
I think it would be great if the solution to this issue was solution #18931. Although the user should be able to manage this.
Checklist
The text was updated successfully, but these errors were encountered: