Bug 337221

Summary:	Paragraph style manager not working right with pre-definied styles
Product:	[Applications] calligrawords	Reporter:	Kruno <kruno0407>
Component:	general	Assignee:	Calligra Words Bugs <calligra-words-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kruno0407
Priority:	NOR
Version First Reported In:	2.8.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kruno 2014-07-08 08:47:10 UTC

If in Style manager I define Next style (e.g. Standard) for pre-defined Heading 1, settings are ignored. Calligra keeps reverting these settings to default, so changing my Next style (standard) to default Next style (Heading 1).

But if I make my own style - thing works good.

Samo thing happens with line spacing - Calligra keeps rewriting my 1.5 spacing to default, no metter I press Apply or just Ok.

Somehow related to bug https://bugs.kde.org/show_bug.cgi?id=331319

Reproducible: Always

Steps to Reproduce:
1. Modify (pre-defined) Heading 1 style in Style manager
2. for Next style define Standard
    (2.1. Define line spacing 1.5)
3. Press Apply/OK
Actual Results:  
Calligra rewrites changes to default

Expected Results:  
When (pre-defined) Heading 1 style is used, style Standared should get activated on pressing Enter (as next paragraph style).

Comment 1 Kruno 2014-07-08 09:15:05 UTC

Just wanted to add: In style manger I can't set paragraph style to justify, it just wont work, it ignores me, but some other features in Style manager work, can't figure out pattern.

So to mention ones more: https://bugs.kde.org/show_bug.cgi?id=331319

Comment 2 Andrew Crouthamel 2018-11-12 02:50:09 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-21 04:20:57 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Justin Zobel 2023-01-02 07:43:49 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2023-01-17 05:16:41 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2023-02-01 05:05:57 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!