On Mon, Mar 09, 2009 at 11:44:31AM +0000, Thomas Adam wrote: > 2009/3/4 David Fries <[email protected]>: > > On Tue, Mar 03, 2009 at 09:41:58AM +0100, Dominik Vogt wrote: > >> On Sun, Mar 01, 2009 at 04:08:57PM -0600, David Fries wrote: > >> > history and bug report: > >> > I just upgraded fvwm and saw an edge bump behavior at the outside > >> > paging border when moving a window. ?When a window was moved into the > >> > panning window the poiner and window would be bumped so the pointer > >> > was moved outside the panning window. ?This jumping was annoying and > >> > was causing me to drop windows a pixel or two from the border, which I > >> > would have to pickup and move again. > >> > >> I don't understand the problem exactly. ?Can you give me precise > >> instructions with a minimal config file? > > > > Just ConfigFvwmDefaults, > > touch /tmp/empty > > ./fvwm -c /tmp/empty > > left click background for menu, click Issue fvwm commands, > > `OpaqueMoveSize 200` ? ?(optional) > > `Move` > > Click and drag from the lower part of the window, and drag it to the > > top of the screen. ?Keep pushing up and you'll see the pointer and > > window jitter as it jumps between the top pixel of the screen and two > > pixels down. > > I bet this is due to panframes. Add to your instructions: > > OpaqueMoveSize 200 > EdgeThickness 0 > Move > > Does it disappear then? (The use of OpaqueMoveSize is completely > unnecessary here, FWIW.)
Yes it is gone. > In which case, the problem is most likely the events the pan window > receives as the window is moved across it (and hence the pointer is > then inside of the panwindow also.) Not no this case. I'm at the top of the top virtual page without edge wrap, which is just the same as any other outside border. Panning frames are only placed on borders which have a virtual page in that direction, the outside border doesn't. > I don't believe your patch to be a good enough fix though for this -- > it seems to be orthogonal to the problem; at least in terms of how I > am able to reproduce it and potentially "fix" the issue. > > -- Thomas Adam Care to explain? It fixes the problems I'm seeing, and I'm not seeing any new ones. Have you tried my patch? What behavior are you seeing before or after? The two files are fixing two separate bugs which I gave in the original e-mail, the virtual.c 1.187 revision masked the move_resize.c __move_loop problem. fvwm/virtual.c revision 1.187 date: 2007/09/11 18:48:57; author: domivogt; state: Exp; lines: +7 -7 * Fixed jumping windows under some circumstances when releasing the button in interactive motion while hitting the desktop's edge. -- David Fries <[email protected]> http://fries.net/~david/ (PGP encryption key available)
