Bug 65684 - EDITING: Rotation of cropped images - Center of rotation strangely located
Summary: EDITING: Rotation of cropped images - Center of rotation strangely located
Status: RESOLVED DUPLICATE of bug 35922
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-06-12 16:27 UTC by deepblue4711
Modified: 2013-09-23 21:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
A presenter file with 2 slides: Slide 1 cropped screenshots - one rotated by 90-degrees; Slide 2 screenshot of result (155.76 KB, application/vnd.oasis.opendocument.presentation)
2013-06-12 16:27 UTC, deepblue4711
Details

Note You need to log in before you can comment on or make changes to this bug.
Description deepblue4711 2013-06-12 16:27:51 UTC
Created attachment 80734 [details]
A presenter file with 2 slides: Slide 1 cropped screenshots - one rotated by 90-degrees;  Slide 2 screenshot of result

Problem description: 
When I am rotating a cropped image the visible part of the image changes. It seems that the center of rotation does not take over the cropping.

Error reproduced with the attached file:
 - MacOSX - 10.6.8 - MacBook
 - Ubuntu-Linux 13.04 - Lenovo Thinkpad
 - no information about Windows

Error appeared with release 4.X

Steps to reproduce:
1. Open a new file in presenter.
2. Include an image (e.g. from clipart gallery)
3. Rotate the image

Current behavior:
Visible area of the cropped image changes

Expected behavior:
The visible area of the cropped image should stay the same being only rotated

Regards
Thomas

              
Operating System: Mac OS X
Version: 4.0.0.3 release
Last worked in: 3.6.6.2 release
Comment 1 Pedro 2013-06-19 13:59:55 UTC
Confirmed also under Windows XP x86 using 4.0.3.3
Comment 2 tommy27 2013-09-23 21:18:38 UTC

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