Bug 342856 - Transform partially lost when *.KRA file saved and re-opened
Summary: Transform partially lost when *.KRA file saved and re-opened
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tools/Transform (other bugs)
Version First Reported In: 2.8.3
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Dmitry Kazakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-14 23:31 UTC by odiyanaperth
Modified: 2021-05-24 08:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description odiyanaperth 2015-01-14 23:31:07 UTC
1. Draw a thin near-horizontal vector line.
2. Select the line.
3. Select the "Transform a layer or selection" tool .
4. Drag the top handle of the transform tool up so that the line becomes quite thickened (it gets thicker, as well as the angle increasing).
5. Save as a *.KRA file.
6. Close Krita and re-open from the saved *.KRA file.
7. When re-opened, the line thickness has been lost - it has reverted to a thin line, although the increase in line angle generated by the transform has been preserved.

Reproducible: Always

Steps to Reproduce:
1. (see "Details")
2.
3.

Actual Results:  
(see "Details")

Expected Results:  
Line thickness increase should have been preserved in the saved and re-opened *.KRA file.
Comment 1 Halla Rempt 2015-01-15 09:32:00 UTC
Hi! Thanks for the bug report! I'm not even sure that the transform tool is supposed to work on vector objects, but it looks like it does, and the result is indeed not saved correctly, so confirming.
Comment 2 Halla Rempt 2015-01-29 14:57:08 UTC
See also the mailing list discussion at 

http://lists.kde.org/?l=calligra-devel&m=142148514020788&w=2
Comment 3 Dmitry Kazakov 2021-05-24 08:38:04 UTC
Hi, odiyanaperth!

I think the bug has been fixed after one of my vector shapes refactorings that happened in 2016 :)

At least the bug is not reproducible anymore :)