Bug 289646 - callouts have different position after load save
Summary: callouts have different position after load save
Status: CONFIRMED
Alias: None
Product: calligracommon
Classification: Applications
Component: path-shapes (show other bugs)
Version: 2.4-snapshots
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-23 08:17 UTC by T Zachmann
Modified: 2021-03-09 01:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Test document (13.68 KB, application/vnd.oasis.opendocument.presentation)
2011-12-23 08:18 UTC, T Zachmann 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description T Zachmann 2011-12-23 08:17:13 UTC 
Version:           2.4-snapshots (using Devel) 
OS:                Linux

When saving callouts that have the line to the left/top the position of the callout is different after saving/loading the data

Reproducible: Didn't try

Steps to Reproduce:
Open the attached document.
Save the document.
Load the saved document.

Actual Results:  
The position of some callouts change.

Expected Results:  
The position of the callouts should stay the sameg
Comment 1 T Zachmann 2011-12-23 08:18:01 UTC 
Created attachment 67044 [details]
Test document
Comment 2 T Zachmann 2011-12-23 08:32:31 UTC 
Git commit f67e979fcde00f020a80664130934d561ce855d8 by Thorsten Zachmann.
Committed on 23/12/2011 at 09:21.
Pushed by zachmann into branch 'master'.

Correctly save position of callouts.

This patch only works for shapes that are not rotated/skewed. This fixes
the most occurences of the bug 289646 -  callouts have different position after load save

@Jan: could you please have a look at the transformed shapes. There is some transformation magic that
I still have a hard time to master.

CCBUG: 289646
CCMAIL: jaham@gmx.net

M  +34   -2    plugins/pathshapes/enhancedpath/EnhancedPathShape.cpp

http://commits.kde.org/calligra/f67e979fcde00f020a80664130934d561ce855d8
Comment 3 Justin Zobel 2021-03-09 01:23:26 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.