Closed GoogleCodeExporter closed 8 years ago
Looking at it with Winspector, I get this:
Start WM_WINDOWPOSCHANGING (1464, -57)
End WM_WINDOWPOSCHANGING
Start WM_WINDOWPOSCHANGED (1464, -57)
Start WM_MOVE(1464, 65479)
End WM_MOVE
End WM_WINDOWPOSCHANGED
Start WM_LBUTTONUP <== move should be finished, right?
Start WM_MOVING (RECT 1464, -57, 1690, 60)
End WM_MOVING
Start WM_WINDOWPOSCHANGING (1464, -57)
End WM_WINDOWPOSCHANGING
Start WM_WINDOWPOSCHANGING (1464, -15) <== where did that -15 came from?
End WM_WINDOWPOSCHANGING
Start WM_WINDOWPOSCHANGED (1464, -15)
Start WM_MOVE(1464, 65521)
End WM_MOVE
End WM_WINDOWPOSCHANGED
Confirmed thus also on a single monitor, XP x86 SP3 machine.
Also, funnily enough, if I run this in debug and set a breakpoint in OnMove,
the bug
doesn't happen. It seems to be related to the order in which OnMove and
OnWindowPosChanging are processed. Also, I don't see a return for WM_LBUTTONUP,
but I
don't know whether that's important.
Original comment by lauren...@gmail.com
on 14 Oct 2009 at 11:33
I've reproduced this bug in this version: Rainmeter-0.14.1-r133-32bit-beta.exe
. The
latest official 0.14 version doesn't have it.
Original comment by lauren...@gmail.com
on 18 Oct 2009 at 10:44
Fixed. (r313, r317)
Original comment by spx268
on 29 Jan 2010 at 12:13
Original issue reported on code.google.com by
lauren...@gmail.com
on 13 Oct 2009 at 11:17