Bug 74289

Summary:	UI
Product:	LibreOffice	Reporter:	sunmoon51
Component:	Draw	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID
Severity:	major	CC:	bfo.bugmail
Priority:	medium
Version:	4.2.0.4 release
Hardware:	x86-64 (AMD64)
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description sunmoon51 2014-01-31 18:24:53 UTC

This is repost of Bug 52234 of 3.5.1 release. Sorry. It's a pity the bug is not fixed since 2012, July.

Suppose you have a rectangle. You want to move it. You place mouse cursor over the rectangle and left click it. Wait a moment. The cursor changes and you move the mouse. You do not see object shadow moving. This is the bug. You release mouse button and the rectangle is in the new position. But you were not able to position the rectangle because the object shadow was invisible while dragging.

But: move the mouse over the rectangle and left click mouse while moving. Guess what? The object shadow is visible and you can position the object. So this is a difference.

The effect is even more visible while option "Snap Lines when Moving" is selected. You can see snap lines vanishing after a part of the second after you left click your mouse while the mouse is not moving. When you start with moving mouse you can see snap lines moving together with the object shadow as it should always be.

The effect is most annoying while trying to move lines. Most times you end up with a line moving without shadow. Therefore I assume fixing this bug is kind of important issue.

Comment 1 Jorendc 2014-01-31 18:53:00 UTC

Please do not re-report bugs. the bug is filed and is still open. 1) you wait until someone invest time in it (we have 6000 bug reports). 2) fix it yourself. ranting and create dupes of a bug is really not the good way.

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

Comment 2 bfoman (inactive) 2014-01-31 18:56:31 UTC

Reposting bug reports is not needed - please add a comment to original report instead if you want to add something. Your original bug was confirmed and is awaiting for a volunteer developer who would like to fix it.
Marking as INVALID as this is a clone of bug 52234.