Version 25.2.6.2, Arch Linux.
There was a time when the next style attribute of a new style would default to the new style. Now it seems to default to the default name of the new style, but this is not updated when the new style is given its intended name. Furthermore, because the new style has not yet been created it is not possible to manually set the next style to be the name of the new style. Instead it is necessary to select an arbitrary existing style, save the new style, then reedit it to change the next style to be the same as the newly created style.
Does anyone else see this behaviour, and should it be considered a bug?
There is an undocumented, feedback-less behaviour in style dialogs: as long as you don’t “touch” setting they remain in “transparent” state, i.e. ineffective.
Consequently, don’t enter anything in the Next style entry box. On creation, this box is meaningful only if you want the next style to be different from the created one. Have you followed this track?
When you press OK in a style dialog, Writer does a lot of post processing before registering the style. In particular it computes consistent values of untouched parameters.
Indeed, LO in general has a detrimentl weakness: it has no way to give a visual feedback for “transparent” attributes.
From the “Styles and formatting” dialog I right-click a parent style and choose “New”.
The Paragraph style dialog opens, with “Untitled1” in both the “Name” and “Next style” fields. The tab list appears greyed, but is actually active.
I type a name for the new style. Next style remains “Untitled1”.
I click “Indents & Spacing”. A message box displays"This Style does not exist."
Incidentally, I don’t know what the motivation was for moving the tab selection from the top to the left of the dialog, but it has made its use significantly more awkward and time-consuming.
Mmmh! Weird. Proceeding as you describe, I have no alert when switching to Indents & Spacing. When I switch back to General, Next style now displays the new style name.
Did you update recently? You are at same release as mine (under Fedora 42). Though no reboot is required under Linux, you could force one. If problem persists, does it occur in “safe mode” (see Help>Restart in safe mode). Backup your user profile just to be safe.
1 Like