MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
Improve Note Input's caret display ... so it's immediately and always informative.
In MuseScore 4.4:
Note Input's faint blue "pending note value caret" displays only after the user moves their pointer. This leaves the user blind to the pending note value to-be-entered on click. As a workaround the user can shift their visual focus to the Toolbar.
The user should see the note value without needing to move their pointer or a glance to the Toolbar. When teaching MuseScore to a student yesterday, or pressing q in Note Input she said, "Wait, nothing's happening."
Please see the attached video where the blue caret only shows after a mouse move.
• on n (I.e. when first entering Note Input) the blue caret shows the default quarter note only on moving the mouse
• on pressing q or w. Again there's no feedback via the blue caret until the user moves the pointer.
As an example:
Starting with a new score (with the default quarter note input value)—and with my hand off my mouse—there's no blue quarter note caret, and pressing q q q shows no indication of a change in the pending value of the to-be-entered note. And no show when continuing with w w w.
Recommendation:
Displaying the blue caret on n (entering Note Input), on q or w, and likewise when the user presses a value specific key such as 4 3 2 1 ... which also fail to update the caret on keypress.
Problem to be solved
In Note Input mode: Always have the blue caret the show the value of pending note, so the user doesn't have wake the caret by jostling their mouse. This would also relieve the user's tendency to glance up to the toolbar and immediately back to the entry point. Whenever I teach someone to user MuseScore I see them struggle with these issues, which slow them down considerably during Note Input.
Prior art
No response
Additional context
No response
Checklist
[X] This request follows the guidelines for reporting issues
[X] I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
Improve Note Input's caret display ... so it's immediately and always informative.
In MuseScore 4.4:
Note Input's faint blue "pending note value caret" displays only after the user moves their pointer. This leaves the user blind to the pending note value to-be-entered on click. As a workaround the user can shift their visual focus to the Toolbar.
The user should see the note value without needing to move their pointer or a glance to the Toolbar. When teaching MuseScore to a student yesterday, or pressing q in Note Input she said, "Wait, nothing's happening."
Please see the attached video where the blue caret only shows after a mouse move.
https://github.com/user-attachments/assets/da569fc0-77d2-4413-8b24-61f0828314df
This lack of instant visual feedback happens:
• on n (I.e. when first entering Note Input) the blue caret shows the default quarter note only on moving the mouse
• on pressing q or w. Again there's no feedback via the blue caret until the user moves the pointer.
As an example:
Starting with a new score (with the default quarter note input value)—and with my hand off my mouse—there's no blue quarter note caret, and pressing q q q shows no indication of a change in the pending value of the to-be-entered note. And no show when continuing with w w w.
Recommendation:
Displaying the blue caret on n (entering Note Input), on q or w, and likewise when the user presses a value specific key such as 4 3 2 1 ... which also fail to update the caret on keypress.
Problem to be solved
In Note Input mode: Always have the blue caret the show the value of pending note, so the user doesn't have wake the caret by jostling their mouse. This would also relieve the user's tendency to glance up to the toolbar and immediately back to the entry point. Whenever I teach someone to user MuseScore I see them struggle with these issues, which slow them down considerably during Note Input.
Prior art
No response
Additional context
No response
Checklist