Bug 88684

Summary: Embedded objects move jerkily when dragged
Product: LibreOffice Reporter: Andy <silvandy>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: medium    
Version: 4.4.0.2 rc   
Hardware: All   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: A calc file with a bitmap inside that is moving an awfully jerky way when dragged around
a short video showing how badly the picture inside the calc file moves around. watch it keeping an eye on the pointer movements: those of the of the bitmap do not follow,and tend to be only horiz/vert

Description Andy 2015-01-22 01:09:11 UTC
Created attachment 112630 [details]
A calc file with a bitmap inside that is moving an awfully jerky way when dragged around

Open the attached Calc file. Inside you'll see a bitmap. Point to it with the mouse, click and drag. As you move the mouse, you expect the picture to follow this movement smoothly: Instead, the movement is jerky and it is impossible to put the object exactly where you would like to. After some fiddling, you'll revert to moving the object with the arrow keys not to waste a lot of time.

Please notice that the program settings like "line up to the grid" etc. are all disabled, so the object should move in a regular way, faithfully following the mouse movements.

This jerky movement problem appears in the Draw Module as well, and perhaps is even more annoying there, given that working in Draw you would probably drag object around very often.

To understand what I mean by jerky movements, watch the screen video capture I have attached.
Comment 1 Andy 2015-01-22 01:14:16 UTC
Created attachment 112631 [details]
a short video showing how badly the picture inside the calc file moves around. watch it keeping an eye on the pointer movements: those of the of the bitmap do not follow,and tend to be only horiz/vert
Comment 2 tmacalp 2015-01-22 01:52:07 UTC
This has been fixed and should be fixed for the release of 4.4.0.

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