Would anyone be against clearing the palette search when initiating search by its keyboard command?
When utilizing the keyboard command to initiate palette searching, I've so far not once wanted to continue where I left off after typing in a previous search. That's to say, I clear the palette search text every time I initiate a new search. This is especially true now that the command to insert the most recently selected palette item (or first if not selected yet) command exists since 3.3.x, and on the rare occasion that there is anything else useful from the search results for later use, I use mouse activity to change the selection rather than try to navigate around with tabs and arrows.
I wonder if anyone would be against having a clean search text every time pressing the search text command. That isn't to say that if the user clicks in the search text that it would be erased, but only the keyboard command to do so. It would speed up, not much, but slightly, my activity using search functionality. Was thinking about doing a little pull request instead of doing my own local build for this since it could be in agreement with how others use it.
Comments
I think that's a great idea. You have my vote.
Wouldn't simply preselecting the entered text be quite standard/aligned with other text entry functionalities (I mean in general, not specifically in MuseScore)?
Meaning that if you just need a completely different text you can just type immediately that will overwrite the existing one.
If you want to alter the existing one you must first move the cursor (which will deselect the text). If you want to add letters at the end of the existing text you need to press the end key once before typing to force deselection.
In reply to Wouldn't simply preselecting… by frfancha
That's my vote. It's useful to mimic how similar things work elsewhere unless there is a great reason not to, and I don't see one here.
In reply to Wouldn't simply preselecting… by frfancha
That's even better.
In reply to Wouldn't simply preselecting… by frfancha
Yeah, makes sense to be in conformity with default application behavior, and this would serve the same sought functionality. Thanks.