Increase maximum value for frame radius in Inspector for text elements

• Feb 7, 2019 - 02:01
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Randomly
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
easy

With MuseScore 2 it is possible to make beautiful rounds when placing a frame around a text:
 
Arrondis_planteurs ms2.png
 
On the other hand, it has become impossible with MuseScore 3. Even with an excessively large value, the rounding is barely visible :
 
Arrondis_planteurs ms3.png

(The 2 pictures show the same frame created with MuseScore 2 and the same one opened with MuseScore 3).

Worse, in some cases the file created with MuseScore 2 does not open with MuseScore 3 and even causes it to crash. If it opens the frame is resized.
See this thread: https://musescore.org/node/283646 and try to open the first attached file with MuseScore 3.

Comments

• Aug 30, 2019 - 10:52
Title Can not round angles;) ⇒ Imported 2.x score crashes after a while, and also when saved; text frame appearance doesn't match values in Inspector?
Status needs info ⇒ active

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.8162, revision: 60e5389

  1. Open the score indicated in the OP (take the reset, say). Compare it to the same file in 2.3.2.
    Expected result: The Title text should look the same in both cases?
    Actual result: The property values of the Title text frame are the same in both versions, but the frame has lost much of its rounding in MS3.
  2. Save the file. Note: The program can also crash without warning after a while.
    Result: CRASH.
  3. Try to reopen the file.
    Result: The file has been corrupted and won't open.

Reply

• Aug 30, 2019 - 10:53
Title Imported 2.x score crashes after a while, and also when saved; text frame appearance doesn't match values in Inspector? ⇒ Imported 2.x score crashes after a while, and also when saved; text frame appearance doesn't match values in Inspector

Reply

• Aug 30, 2019 - 15:54
Title Imported 2.x score crashes after a while, and also when saved; text frame appearance doesn't match values in Inspector ⇒ Increase maximum value for frame radius in Inspector for text elements
Severity S2 - Critical ⇒ S5 - Suggestion
Priority ⇒ P2 - Medium

The change in the frame is by design. It was a bug in MuseScore 2 that corners got rounder and rounder as the frame grew (and if you weren't careful, the text would even extend beyond the frame). That bug is fixed, so a given radius value now produces the same results regardless of the size of the frame. This means if you want extremely round corners, you need extremely large radius values. So I'm changing this to a suggestion to allow larger values in the Inspector.

The crash is almost certainly unrelated and should be reported separately. The parts are clearly corrupt in this file, this is plainly obvious in MuseScore 2 as well. So crashes are going to be somewhat inevitable at some point. I can make it crash in MsueScore 2 just by clicking one one of the corrupt measures.

Reply

• Aug 31, 2019 - 05:17

Correct. We actually do some processing of this number n the code I think before passing it to Qt, to help ensure consistency across different sizes, and I don't know what Qt's own maximum value is. But presumably it's possible to allow larger.

Reply

• Dec 16, 2019 - 13:59
Status PR created ⇒ fixed

Fixed in branch master, commit 4016216323

_fix #283653: increase maximum value for frame radius in Inspector for text elements

The default maximum value in Qt designer is 99, this remains unchanged for the corner radius setting for texts. #283653 suggests a bigger maximum value._

Reply

Fix version
3.4.0