Cut text within staff text hangs program; copy/paste doesn't work

• Nov 29, 2018 - 09:44
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
MuseScore

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0., revision: 3543170

Repro steps:

  • Add a staff text with CTRLT
  • Enter some text.
  • Select the entered text with CTRLA
  • Copy with CTRLC
  • Add second staff text with CTRLT
  • Paste with CTRLV

Expected: The text get copied into the second staff text.
Actual: The second text remains empty.

Comments

• Nov 29, 2018 - 17:03
Priority ⇒ P1 - High

Note you don't even need to create the second staff text - copy/paste doesn't work within a single staff text, either. Nor does it work for other text elements I tried, except for frame text.

Reply

• Dec 3, 2018 - 15:03
Title Copy & Paste text does not work for System Text / Staff Text ⇒ Cut text within staff text hangs program; copy/paste doesn't work
Priority P1 - High ⇒ P0 - Critical
Severity S3 - Major ⇒ S2 - Critical

Copy merely doesn't work. "Cut" hangs the program, and hard - I can't even "X" out of it, need to close from task manager :-(

Reply

• Dec 4, 2018 - 15:27

For me, the following hangs:

1) default empty score
2) click first empty measure, Ctrl+T
3) type "staff text"
4) hit shift+left four times to select the word "text"
5) Ctrl+X

It's a really hard hang; it also renders the debugger (QtCreator) inoperative, and it often takes multiple attempts to kill in task manager (Windows 10). I'd think it was a tight loop somewhere but CPU activity isn't actually spiking at all; seems to be waiting on something.

Reply

• Dec 4, 2018 - 16:08

Well, for me the same operations really cut the text with no hanging. I cannot paste it though without the above fix but no hang occurs.

Reply

• Dec 4, 2018 - 16:42
Priority P0 - Critical ⇒  

It seems to only hang when using my own self-built executable (and only when actually running it under the debugger). When I single-step through the code, I see it hangs in a Qt function. I'm using a slightly older version of Qt than the official builds, so at this point, I think it's a non-issue.

Reply