On 20/12/2018 01:58, Paul A. Rubin wrote:
Hi all,
I just installed 2.3.2 and I have a question regarding change tracking.
I'm not sure if this is a change in 2.3.2, or if it's always been this
way and I just never tripped over it. If I have change tracking turned
on and I change the font of a selection (for instance, by clicking the
emphasis button, or via the text style dialog), the selection is /not/
marked as changed. That's very unhandy ...
This has always been that way and been on the enhancement request list
for a long time: https://www.lyx.org/trac/ticket/1043. Tracked changes
is steadily improving but slowly and it has not come so far yet.
... but not as unhandy as the new feature in the text style dialog that
causes it to pick up the current settings of the selected (rather than
initializing everything to "No change"). I frequently change just the
series to bold and then use the apply last style button repeatedly. That
will now screw up other text that I'm making bold if it has any
characteristic different from the first text I made bold. Changing each
of the other boxes in the style dialog to "No change" is a royal PITA.
Assuming this is the new normal for the style dialog, any chance there
could at least be a button at the bottom that would clear all settings?
Maybe you can file a bug report with the keyword "regression" for this?
In the current stable development version the font dialog sets all
settings to default if none have been changed (see
https://www.lyx.org/trac/ticket/11385). That is already an improvement,
I think.
But this does not get you what you want. I think the idea behind the new
dialog is to show users the formatting of the current selection which is
how it works in other writer apps. That seems sensible. And writer apps
normally apply the text properties from one selection to another. That
is also how it works now.
What you request is nothing I have seen in other writer apps but I agree
that it is a desirable feature and this is a regression from earlier
versions of LyX. Can you can file a bug report with the keyword
"regression".
Daniel
