lyrics verse number of different style by default
Reported version
3.0
Priority
P1 - High
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
write 1st verse (without numbering it)
write 2nd verse (without numbering it)
write 3rd verse (without numbering it)
Then add the number at the beginning of each verse
Result :
the style of the 1st number is different from the other
Note : it doesn't happen if I enter the number of each verse first
| Attachment | Size |
|---|---|
| lyrics.png | 8.48 KB |
Comments
I can't see your image, and I can't reproduce a problem myself. Can you attach your actual score?
In reply to I can't see your image, and… by Marc Sabatella
I wasn't able to reproduce exactly the same issue but in the file attached, you can see that the 2nd verse style is different from the other.
The "1." and the "3." indeed uses a different font, not FreeSerif like it should but, in my case, "Agency FB", the top one in my list of fonts.
I can reproduce if I double click the "2.Ly" at the "2", so that the cursor shows before the 2 and then start typing.
If I double click anywhere else in that syllable and than move the cursor to the start, it stays in FreeSerif though
OK, so this seems like another manifestation of #281831: text cursor before first character of a text element or before a special character of text aren't initialized to text element's default, and as such should now be fixed in current master. I have trouble reproducing this even in 3.0.2 because it is so sensitive to exactly where you double-click, and I suspect screen resolution actually plays a role in that making it easier for some people to reproduce than others. I can reproduce about 1 try in 20 using 3.0.2, but so far can't reproduce at all in a build from master.
If someone can reproduce in current master, we can set this back to active, or re-open #281831: text cursor before first character of a text element or before a special character of text aren't initialized to text element's default, but otherwise, I think we can close this.
Ah, yes.