Tool tips for key signature in the new score wizard or master palette don't show accidentals
Reported version
3.0
Priority
P1 - High
Type
Graphical (UI)
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
Instead of the flat the following characters are displayed: â™.
In the case of the sharp, it's the same but with an adittional upper dash.
Not an issue of the default font, as in the last stable version of MuseScore 2.3.2 the alterations appear correctly.
Used language settings: English US
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4516, revision: 59a11cd
| Attachment | Size |
|---|---|
| Pantaila-argazkia (8).png | 125.56 KB |
| Pantaila-argazkia (9).png | 126.3 KB |
Fix version
3.0.1
Comments
What OS, and what font do you have installed as your default system font? Probably it lacks the flat sign.
And what language setting, Basque? It possibly is a translation issue
In reply to What OS, and what font do… by Marc Sabatella
Thanks!
Updated
Updated what? Problem solved?
In reply to Updated what? Problem solved? by Jojo-Schmitz
Sorry, it's my first time using the issue tracker.
I meant that I've updated the info but the problem is still around.
What language setting? Is it an issue with the translations, try US English
In reply to What language setting? Is it… by Jojo-Schmitz
Tried with English US language setting, issue not solved
What system font is used in Edit/Settings/Preferences/Style? Should be MS Shell Dlg 2
Still the case with the RC that just came out?
In reply to What system font is used in… by Jojo-Schmitz
Still the case with the English RC using windows 10...in English of course.
Same question for you then - what font are you using for system dialogs? If it's one that lacks a flat sign, there is little we can do about it.
In reply to Same question for you then -… by Marc Sabatella
I don't know, it's one that works fine in version 2.
See Edit / Preferences, it shows you the current font selection and lets you override it.
In reply to What system font is used in… by Jojo-Schmitz
My system font is MS Shell Dlg 2 and RC didn't fix it.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4747, revision: 96c1f7b
Which version of Windows 10, try running winver to find out. ISTR there was an older Windows 10 that had that font broken
In reply to Which version of Windows 10,… by Jojo-Schmitz
Mine is 1803
Then it got to be something else, on.my Windows 10 1709 those flats and sharps in the time signature palette's tool tips work just fine
Outch! They work in the key signatures palette (of the Basic or Advanced workspace) but indeed not in the new score wizard nor in the master palette! Windows 10 and 7.
For me it works in wizard too.
Which OS, language and font?
Tried Basque and Spanish language settings and it's the same. There's an exception for my MuseScore in all three languages: A major and F sharp minor display correctly.
Yes, that is something I notieced too, there the sharp (♯) it a hash (#), accidentially
My question was meant for Marc though ;-)
In reply to Yes, that is something I… by Jojo-Schmitz
I knew; it only seemed weird to me that those tonalities displayed correctly, and maybe that could be a little extra info to help solve the problem; but I was mistaken: as you said, it's a hash.
came up again in https://musescore.org/en/node/281181
May turn out to have a common root cause with #281137: Chords in french notation are not formated correctly if accented letter expected
I don't think so. Right now, I see a change in last month of November.
Going to narrow down.
yes, looking closer I'm not too sure about it anymore, as it reproduces differently from the other issue
Occurs on November 30
Ok with this one: e746352
And not with: 070f767
So, maybe here ? ;)
https://github.com/musescore/MuseScore/commit/1bf01544d9566bf66c662012b…
But also seems to be a Windows issue (for Mac I don't know), accidentals are shown correctly inside the tool-tips with Linux as both with the AppImage and a distribution package of the released version.
In reply to But also seems to be a… by kuwitt
And also seemingly a plain MSVC issue, not with MinGW, where I see those strings even properly translated. But that commit is indeed likely involved. Question is why only MSVC seems to have a problem with those Utf8 strings.
It seems fixed, please check latest development build and reopen if not
Confirmed. As expected again. Thanks.
Automatically closed -- issue fixed for 2 weeks with no activity.