On Mon, Apr 22, 2002 at 03:05:26PM -0400, Dan Espen wrote: > Dominik Vogt <fvwm-workers@fvwm.org> writes: > > On Fri, Apr 19, 2002 at 12:59:10PM -0400, Dan Espen wrote: > > > Why can't the menu code be in a module? > > > > Of course menus *can* be a module. It's just that the menu code > > was not written to run independently of fvwm and is thus > > interwoven tightly with fvwm's data structures. > > Well, and as long > > as menus grab the pointer and the keyboard, processing module > > messages is pointless since the function execution code needs (?) > > to grab the pointer too. > > I don't think I understand the point about the grab. > Its OK for menus to freeze FVWM so the grab should be OK.
When any client grabs the pointer, fvwm basically stops processing most module messages too, at least if modules call complex functions. > I think putting the menu code in a module might simplify tear > off menus. I'm not sure of all the details but it just seems > like it might. Perhaps another copy of the menu module could be > started to handle the torn off menu (without grabs once its torn > off). Fvwm menus need to grab the keyboard to work properly. Pure mouse oparable menus would be useless to me. 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]
