Bug: Hit Enter in tempo marking text box and MuseScore crashes
I posted a similar report about rehearsal marks several months ago. Apparently you're supposed to click outside the text box to confirm the changes. Great, that works. But single-line text fields in virtually every program also accept Enter to confirm the changes.....if you do this in MuseScore's tempo marking text boxes or rehearsal marks, it crashes. I'm guessing in other similar text boxes too, but haven't checked.
I mean...it's OK if Enter just does nothing, and you have to click outside, but crashing?? The rehearsal mark text box bug has not been fixed either. I have the latest version as of this posting.
Please take a look! Thanks!
Comments
Probably best to report this on GitHub, https://github.com/musescore/MuseScore/issues/new/choose
"But single-line text fields in virtually every program also accept Enter to confirm the changes"
Besides the crash:
Tempo marking text boxes are not single-line text fields, so Enter makes a line break as in every common text program.
In reply to "But single-line text fields… by Pentatonus
Ok, but they should be single-line fields, why would there need to be any more lines? Same with rehearsal mark text boxes.
In reply to Ok, but they should be… by seejayjames
Well, sometimes it is usefull to have them as multiline. At least there's no reason to prevent that
In reply to Ok, but they should be… by seejayjames
"why would there need to be any more lines?"
Because, for example, you may have something like "Andante scherzando, non tropo vivo, " followed by a metrical indication in brackets and you need to fold it onto two or even three lines to avoid a clash with another following tempo indication 4 bars later
With rehearsal marks, they are useful to indicate things like "end of first subject", "second subject with variation", "recapitulation in tonic", or other similar signposting longer than a simple letter/number. They need be compact so that they can be located precisely but may need folding so they don't hang over into the margins.
In reply to "why would there need to be… by SteveBlower
Ah! I can see how that would be helpful. Makes sense.
I'm not encountering any problem with multi-line tempo or rehearsal markings. Please attach the score you are having trouble with and give precise steps to reproduce the problem so we can attempt to reproduce the issue before you open an issue on GitHub. Also say what OS you are on.
Note that as mentioned, these aren't "single line text fields" - they are places where you can enter arbitrary text or multiple lines, by design.
In reply to I'm not encountering any… by Marc Sabatella
Here's the score, it's just a blank one with several different text elements: title, subtitle, composer, tempo marking, rehearsal mark, and generic staff text. ALL of them cause a crash if you hit Enter when editing! I'm guessing other text elements will too.
I'm on Windows 11 Home, version 22H2, OS Build 22621.1778.
In reply to Here's the score, it's just… by seejayjames
Thanks for the score. None of these crash for me, so the next thing to figure out is what's wrong with your specific installation. Two things to try:
1) Uninstall / reinstall
2) If that doesn't fix it, Help / Revert to factory settings
Another question - what physical keyboard is this? Something built into a laptop, a wired desktop keyboard, wireless, etc? Also, does it have one or two Enter keys (one possible labeled Return), and if two, which one are you using, and does it still crash if you use the other? Is the layout US QWERTY or something else? Anything unusual about your keyboard settings, like maybe you're using a right-to-left language setting?
In reply to Thanks for the score. None… by Marc Sabatella
1) Uninstall / reinstall
2) If that doesn't fix it, Help / Revert to factory settings
Did both. No change.
Physical wired desktop keyboard. Both versions of the Enter key (one on numpad) crash. I use DVORAK layout, but Enter is the same. I also switched to QWERTY just to test---no difference.
Are you on Windows 11 too? This is really strange...
In reply to 1) Uninstall / reinstall 2)… by seejayjames
I have a Windows 11 system, as well as Linux systems. And there are millions of other Windows 11 users. So the trick remains figuring out what is unique about your system.
No special input method line RTL or multi byte character input? Do you have a screen reader enabled?
In reply to I have a Windows 11 system,… by Marc Sabatella
Not RTL and no screen reader. I don't know how to check for multi byte character input though.
In reply to Not RTL and no screen reader… by seejayjames
That would be something you'd set up for entry of Kanji or other symbols in languages like Japanese that require more than 256 different characters.
In reply to Not RTL and no screen reader… by seejayjames
One other possible variable: do you have a non-standard font chosen for the UI? The stats bar normally displays the text of the element you are editing, and if that font chokes on the character used in the status bar to substitute for carriage return / line feeds in the actual text, that might explain it. Could be interesting also to try disabling the status bar in the View menu.
In reply to One other possible variable:… by Marc Sabatella
Tried disabling it, still the same result.
Should I still submit a bug report? Seems like it's just something bizarrely quirky with my machine, if others aren't having the issue I don't want to beat it into the ground haha.
Still dosent work
In reply to Still dosent work by laneviewbenf
Are you by chance on Windows, and do you have the accessibility option "text cursor indicator" enabled? This is known to trigger problems in certain applications, including MuseScore. Try disabling it.
In reply to Are you by chance on Windows… by Marc Sabatella
Oh! Yes I do. Am traveling now but will try when I get back. That's probably it bc it's an unusual setting and nobody else seems to be having the issue. Will investigate.
In reply to Oh! Yes I do. Am traveling… by seejayjames
There were maybe half a dozen reports of this, luckily someone figured out this was the trigger. And several others confirmed that turning it off fixed the crash for them.
But there is also at least one report of someone for whom that didn't turn out to be it - he didn't have that setting enabled. I'm guessing it's some other unusual system setting that somehow behaves similarly.
In reply to There were maybe half a… by Marc Sabatella
Yep! Fixed it for me. Thanks for the info!