2005/9/3 David Wu <zeo33x-f...@introspector.net>: > Hi all. > > I use beep-media-player (bmp) as my music player since it supports GTK2. > I have the following problem when I use it under fvwm 2.5.14-1 > > Whenever I drag the main bmp window from point A to point B quickly, the > window is instantly "teleported" from point A to point B without > actually showing the window being dragged. However, i can fix this if I > mouse click the bmp window and hold without moving, and wait > approximately 3 seconds, the window will behave just fine being dragged. > > Im inclined to think that this has something to do with fvwm since both > default windows manager used by KDE and gnome has no such issue with > beep-media-player. > > I understand bmp like xmms both handle their own window, but I've taken > look at the bmp move code and it seems all that its doing is calling > gtk_move_window() which supposedly asks the window manager to do the > moving. I've also tried the stable version of fvwm and it works fine, > but its missing some much desired features. > > Does anyone know what could cause this type of problem? > > Thanks all in advance!
First of all. Sorry for this being a very late reply. I've started to go through old mail which I intended to reply to, that have accumulated over long time. >From my experience with applications that want to handle their own movement, they generally do an EWMH activate window request before the move request. With fvwm this is bad, because that request will trigger the function EWMHActivateWindowFunc, and because of the way function invocations are handled in fvwm, fvwm will try to grab the pointer before invoking the function. A possible workaround for this is to destroy the EWMHActivateWindowFunc. This will generate warnings that the function does not exist, but fvwm will not try to grab the pointer. (It is not enough to redefine the function empty) /Viktor
