MuseScore Freezes upon fingering traversal backwards when nothing there
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
Seems to happen every time, and in that sense might be considered [Critical] since it freezes and potentially could cause someone to lose valuable work/time:
Exact steps for instance:
1) Create new score (grand staff piano in this example)
2) In first measure, create a quarter note, then add fingering number via keyboard shortcut.
3) Edit the fingering-text so that the cursor blinks.
4) Press either [Shift+Space] or [Alt+Left] which is supposed to traverse back to previous fingering.
5) Crashes/Freezes
I've also noticed this happens on occasion when dealing with a second voice, but don't have exact steps for it. I think it has something to do with the fact that the focus is on voice-1 when traversing with the [space]/[alt+arrow] keys.
Comments
With 3.2? If so, a known issue already fixed for the 3.3. See #295107: Navigation shuts down after the last note of a score.
It would be great, BTW, if you could focus testing the on the RC3 for the next few days!
In reply to With 3.2? If so, a known… by Marc Sabatella
Yeah, 3.2.3. Nice to hear it's fixed. Although, it sounds like they eliminated the wrapping functionality of end/beginning of scores. This sounds kind of funny, but I actually use that functionality in 3.2. because at times if I screw up by pressing N while having some particular element selected, or something happens and the score [reverts] back to the beginning again, I can enter into Fingering-text mode quickly and press [shift+space] to get close to where I was if there was fingering involved. Sounds crazy, but it is a workaround in 3.2.3 at least as it is.
I'm a bit weary (ahem) in continuing some work while in an RC or beta, but now that you mention it, maybe i'll from now on double check the RC/master every time i find something wrong first before posting on here as a rule of thumb. Thanks for the reminder, as I don't really think about non-releases.
In reply to Yeah, 3.2.3. Nice to hear it… by worldwideweary
The pressing N jump to the beginning of the score has been fixed in 3.3-RC3 as part of the new note input workflow. It now puts the note input cursor at the beginning for the measure where the hairpin (or whatever) is located, so I don't think you'll miss the wrap function.
It also remembers the last selection, so even if you have nothing selected at all, if you had ever selected something, you won't go to the beginning. Maybe some corner case remains where you get thrown to the beginning, but it should be much more rare now.
Even if it happens, relying on "fingering mode" to get you to the end of the score seems bizarre. Isn't that what Ctrl+End is for? If you have some use case where somehow this isn't what you mean, feel free to start a forum thread discussing the matter - ideally with a specific score and precise steps to reproduce the problem.
In reply to It also remembers the last… by Marc Sabatella
Read the comment : he has never said to jump end of score, he said to jump where he was working, i.e. on the last notes where fingerings were added (last by their position in the score, not last by the time they got fingerings)
In reply to Read the comment : he has… by frfancha
Although another topic in itself, yet that was another reason why I think it's a really bad idea to continue to not implement shortcuts for "next/previous" system with the addition of "beginning and ending" of the score shortcuts. Not as "Page" view but as selection exactly like "go to next/previous measure". Problem though is then there are so many options:
Prev/Next System
Prev/Next Section
Prev/Next Page
Go to Begin / End Score
Quite a bit of commands, though even the functionality without defaults implemented would be a welcomed addition to see in the shortcuts list for customizing workflow.