Bug 74812 - Rotate via sidebar blows object out of visible area
Summary: Rotate via sidebar blows object out of visible area
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 22:26 UTC by OfficeUser
Modified: 2015-01-23 13:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
issue_draw_rotate.odg (8.11 KB, application/vnd.oasis.opendocument.graphics)
2014-02-10 22:26 UTC, OfficeUser 		Details
issue_draw_rotate.odg (8.11 KB, application/vnd.oasis.opendocument.graphics)
2014-02-10 22:27 UTC, OfficeUser 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description OfficeUser 2014-02-10 22:26:16 UTC 
Created attachment 93809 [details]
issue_draw_rotate.odg

Hello,

- open the attached drawing

- select the blue square

- use the rotate wheel in Sidebar

==> The object vanishes from the sreen.

After more investigation I found out that while using the rotation wheel extreme big numbers are set as position values of the object. So the object is not deleted.

Please note: The edit field with the drop down next to the rotation wheel is also affected.

(This should be easy to fix since Impress ist not affected by this bug.)
Comment 1 OfficeUser 2014-02-10 22:27:08 UTC 
Created attachment 93810 [details]
issue_draw_rotate.odg
Comment 2 OfficeUser 2014-02-18 10:09:35 UTC 
Version 4.2.1.1 is still affected.
Comment 3 Buovjaga 2014-10-29 12:05:16 UTC 
Unable to reproduce. As this is set to "All" OS, I set to WFM.

Win 7 64-bit 4.3.2.2 and Version: 4.4.0.0.alpha1+
Build ID: 4586a3f564600f1a0ce15a5cb98868b43bb9351e
TinderBox: Win-x86@42, Branch:master, Time: 2014-10-29_07:28:16
Comment 4 OfficeUser 2014-11-10 19:07:48 UTC 
Can confirm fixed with builds 4.3.2.2 and 4.3.3.2.