Bug 99239 - Cannot assign a numbering level in a custom Style
Summary: Cannot assign a numbering level in a custom Style
Status: RESOLVED DUPLICATE of bug 42920
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 09:41 UTC by Mathieu Tournier
Modified: 2016-04-24 17:21 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Outline_Level_CustomeStyle_Bug (10.48 KB, application/vnd.oasis.opendocument.text)
2016-04-12 09:41 UTC, Mathieu Tournier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Tournier 2016-04-12 09:41:27 UTC
Created attachment 124275 [details]
Outline_Level_CustomeStyle_Bug

Create a document with two custom styles (that inherit from nothing). Style CustomLevel1 and CustomLevel2.

In edit paragraph style -> outline & numbering, select numbering style "numbering 1" for both those new styles.
Now, for CustomLevel1, in style -> outline & numbering, select outline Level = 1.
For CustomLevel2 , in style -> outline & numbering, select outline Level = 2.

Add a line of each style.

Problem :

Even with specifying custom levels, at the end both the lines are level 1.
Of course, it remains possible to modify the level using the IncreaseIndent button of the interface, but the change is not saved in the style (it's just direct formating).

Normaly, applying the style CustomLevel2 should directly put the right level to the text.
Comment 1 Mathieu Tournier 2016-04-12 09:53:53 UTC
Maybe the outline level parameter (that doesn't seem to work) is not exactly the parameter to modify.
But in that case, it seems that today it's not possible to create custom styles that are equivalent to Heading* (even if we use inheritance, that doesn't work)
Comment 2 Buovjaga 2016-04-24 17:21:37 UTC

*** This bug has been marked as a duplicate of bug 42920 ***