Issue 89544 - Rotating anchored picture moves anchor when it shouldn't
Summary: Rotating anchored picture moves anchor when it shouldn't
Status: CLOSED DUPLICATE of issue 8303
Alias: None
Product: Calc
Classification: Application
Component: formatting (show other issues)
Version: OOo 3.0 Beta 2
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-16 08:09 UTC by ezza
Modified: 2008-07-18 09:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Testcase showing anchored picture before & after rotation (24.95 KB, application/vnd.oasis.opendocument.spreadsheet)
2008-05-16 08:14 UTC, ezza 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ezza 2008-05-16 08:09:31 UTC 
In calc, for pictures set to "Anchor = To Cell", if you rotate the picture, then
the anchor for the image will move to another cell instead of staying where it was.

Example:
Paste image into a cell in the middle of the page.
Note anchor position
Rotate image eg. 90degrees (Right click on image > Position and Size > Rotation
> Angle=90degrees ).

Result:
Anchor for image has moved to a different cell (usually the cell wherever the
top-left of the image is).

Expected Result:
Anchor should be in the same cell it was before.

I will attach a test case with two worksheets, one with the original & the 2nd
the rotated version.
Comment 1 ezza 2008-05-16 08:14:46 UTC 
Created attachment 53697 [details]
Testcase showing anchored picture before & after rotation
Comment 2 ezza 2008-06-20 11:27:17 UTC 
Confirmed issue still present in 3.0 beta, changing version.
Comment 3 ezza 2008-07-16 08:34:36 UTC 
Confirmed with beta2. This might be related to Issue 85791 (anchored cell moves
when row height is changed)
Comment 4 oc 2008-07-18 09:13:11 UTC 
This is a duplicate of #i8303 (same technical reason)

*** This issue has been marked as a duplicate of 8303 ***
Comment 5 oc 2008-07-18 09:13:48 UTC 
closed because duplicate