On Thu, Apr 25, 2002 at 12:24:25PM +0100, Tim Phipps wrote: > fvwm-workers@fvwm.org wrote: > > >On Tue, Apr 23, 2002 at 06:05:06PM -0400, Dan Espen wrote: > > > >>If I'm on the right track, then I think the menu would have to release > >>the grab once the menu is torn off > >> > >Well, it does release the grabs. But as it is now, whenever the > >pointer enters a tear off menu, fvwm makes the grabs again. As > >long as fvwm is in the menu loop it doesn't really matter if the > >grabs are made or not - it can't handle module input anyway in > >that code. > > > I think there might be a bug in the grabbing and it may be the reason > I'm seeing it as a problem. I don't mind fvwm stopping module messages > when the pointer is on the torn-off menu but it seems to keep the grab > when the pointer moves off and it only releases it when the pointer > enters another window. > Normally the grab is released when the pointer leaves the torn off menu > but if you use the keyboard to go from the torn off menu to a sub-menu > and the use the keyboard to go back to the torn off menu and then move > the pointer off the torn off menu the grab remains. You can see the grab > is active because the cursor stays the same as on the menu.
Fixed. The although the grab was released, the pointer was immediately regrabbed because the menu code did not remove EnterNotify events from the queue. These were processed later by the main loop although the window had long been left again. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
