compiz team mailing list archive

[Miklos Juhasz <764330@xxxxxxxxxxxxxxxxxx>]

@Daniel:

I would still prefer to use your fix as the best available solution for
now but I'd like to fix the Alt+F7 move behaviour.

By debugging move.cpp a bit I checked the difference between mouse and
keyboard movement. It turned out that

- when Alt+F7 is pressed moveInitiate is called and ms->lastRootX gets updated to the current position of the pointer, say 1012
- then the pointer turns into a hand and jumps to the middle of the window to be moved
- when I press the arrow buttons for the first time updateMotion gets called and in there pointerX has the value where the pointer is _after_ it jumped to the middle of the window to be moved (say 362) therefore moveHandleMotionEvent thinks that the window has to be moved by 1012-362=650px and the window jumps to the left, partly out of the current workspace.

So, in short, when Alt+F7 is pressed the ms->lastRootX should be updated
to the pointer position when it's _already_ in the middle of the window
to be moved, not where it was before we initiated the movement. (Same
goes for y values of course).

Do you have any idea how to do this?

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/764330

Title:
  [regression] Moving windows lags behind the mouse by 1-2 seconds;
  appear to freeze when dragging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/764330/+subscriptions