Actions applied during text editing more automatically revert on return to normal mode

• Oct 11, 2019 - 14:04
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

I'm currently using MuseScore 3.2.3.7635 (latest version).

If you are entering chords into your score and the cursor is hovering over the score (ready to input a chord name), any other action you take, like dragging in bar lines or repeats or expressions will automatically revert when you click on the score and exit "chord entering mode". I've attached a video.

The work around for this is to exit "chord entering mode" before adding barlines, repeats, etc but I think this is something you should address in the next build. Thanks!

Comments

• Oct 11, 2019 - 15:21
Title Actions Automatically Revert When Chord Entered Mode Is Engaged ⇒ Actions applied during text editing more automatically revert on return to normal mode

Indeed it's not just the Inspector as we have been assuming, so disabling the Inspector isn't the solution I had thought it might be. We could disable more operations, but maybe we really need to ask how this is happening. I wonder if it is due to this change: https://github.com/musescore/MuseScore/commit/e5d8d86d7d4d0d49ead7e8dbe…? Either that or the change that produced the code this is replacing.

Reply

• Oct 11, 2019 - 15:29
Frequency Few ⇒ Many
Regression No ⇒ Yes
Workaround No ⇒ Yes

Not the case in 2.3.2 at least (don't have a 3,0 version to check, above mentioned change was in 3.1), so certainly a regression
Workaround is of course to first leave text edit mode

Reply

• Feb 22, 2020 - 09:17
Status fixed ⇒ active

This fix causes a crash inside Qt with the following assertion failure:

QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0

Steps to reproduce:

  1. Create or open a score with at least one text element.
  2. Double-click a text element in the score.
  3. Click outside the text element to cancel the edit.

The crash happens 100% of the time, and has been confirmed by @dmitrio95 in the MuseScore Developers Chat to be caused by this PR.

Reply

Fix version
3.5.0