On 2008-03-31 (Mon) 20:17:11 [-0400], Benjamin Karhan wrote: > > i've noticed that fvwm 2.5.25 (and the recent snapshots, like 20080322 > and 20080330 specifically) exhibits a somewhat aggravating > behavior with window event handling (not present in the 2.4.x branch > definately). > snip details of weird window/mouse behavior > > anyways... just wanted to bring it to everyone's attention... > in the hopes that it may eventually warrant some fixing... >
I'll pile on and say that with 2.5.25 on Slackware 12.0 I get a problem that I've gotten (and reported) before, which is to say that a click on the desktop with the mouse produces no effect until the mouse is moved at least a pixel and that holding a menu open results in 100% CPU usage for the duration of the hold. Using the pager does not cause this and a 'torn off' (backspaced) menu does not cause this unless the mouse is moved into the torn off menu. IOW, some kind of 'grabbing the X server == grabbing the CPU' and 'mouse is inactive until moved' problem or something. I don't know if this is related to the OPs issue, but sounded related enough to remind me of my issues.
