Adjusting measure width with } shortcut creates many extra zeroes in "Measure width" property
Reported version
4.0
Type
Functional
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
GitHub issue
Regression
Yes
Workaround
Yes
Project
Using MuseScore 4 in Windows 11.
Steps to reproduce issue:
- Create a new blank score
- Select any measure, and increase the measure width a few times using } ( Shift + ] ). It's also noted as "Increase layout stretch" under Format > Stretch.
- In the Properties panel, under Appearance, the measure width will read as something like "1.2000000000000002" instead of "1.2".
The workaround is to just manually type 1.2 into the "Measure width" box to fix the issue.
| Attachment | Size |
|---|---|
| measure width.png | 8.91 KB |
Comments
I can reproduce this on Windows 10. Possibly a floating point precision issue?
Same issue - also windows 10. I wonder if there are actual resource draining implications or if it's just somehow outputting the number incorrectly by appending the first decimal place at the end (eg:1.5000000000005, 1.160000000000016)
As this issue tracker is being discontinued, it is advisable to report this issue on GitHub
In reply to As this issue tracker is… by Jojo-Schmitz
This has now been posted on github, for future reference:
https://github.com/musescore/MuseScore/issues/17013