Formatting text is not working properly

• Sep 4, 2016 - 10:35
Reported version
3.0
Type
Graphical (UI)
Severity
S4 - Minor
Status
closed
Project

Hi,
Open the attachment.
See, that the font used in the lyrics is not the same for both lines 1 and 2.
In line 1, the FreeSerif is used, in line 2, the Tahoma is used.

Select the lyrics, right click your mouse, and select the option 'Select all similar elements'. All lyrics are selected (blue). Then, please select with the right click the option "Text properties'.

Check, that for both lines (odd and even lines) the font is Tahoma. Press OK to apply these fonts to both lines.
See, that the lyrics are not changed to the right font (Tahoma).

Thanks
Theo

Attachment Size
Tel uw zegeningen2.mscz 18.51 KB

Comments

Not specific to the current nightly (same with 2.0.3)

I don't really know which is the expected result (bug or not?) with your procedure, but it works (return in Tahoma font for the first verse) by doing this:

1) Right-click on a lyric first verse -> Select -> More -> Tick " Same subtype, Verse1" -> Ok
2) In Inspector: click on "Reset text to Style"

Maybe another way?

I can only confirm that lyrics formatting using the Styles dialogue works as expected in 2.0.1, so if there is a bug, it appears it was introduced after that version. However, like Cadiz 1, I am not certain about some of what's happening/expeceted here.

1. Upon opening the score, I found the text styles for both odd and even lines of lyrics are set to Tahoma, however the text properties for every syllable of verse 1 are set, as mentioned, to Free Serif, and for verse 2, to Tahoma.

2. One step in the OP's procedure to reproduce the problem is unclear--once one has selected all similar elements, a right-click on an individual lyric syllable selects only that single syllable for editing. In fact, I have found no way to select all the lyrics in a single verse and edit their properties collectively. Perhaps that's different in the nightly used by the OP...?

Text Properties is indeed not meant to affect any but the "current" element, not all selected elements. While it seems logical to want it to affect all selected elements, there are issues with this is they are not currently all the same - we don't really a way in Text Properties to handle fields with varying values (whereas we do in the Inspector, for instance). See #24436: Changes made in Text Properties do not affect all selected elements.

So I guess what is being reported here is a duplicate of that? Basically, one is expecting Text Properties to apply to a multi-selection, but it doesn't, right? This was no different in 2.0.1.

I have a hunch that it might be a bit more complex than just moving the properties dialogues to the inspector. For instance, how would that apply to list, range, and context-menu selections equally? It is currently possible to make a 'list selection' of a number of different elements which do not share the same types of properties.

list selection.png