On Fri, Apr 19, 2002 at 12:59:10PM -0400, Dan Espen wrote: > Dominik Vogt <fvwm-workers@fvwm.org> writes: > > On Fri, Apr 19, 2002 at 04:01:48PM +0100, tim phipps wrote: > > > Configuration Information [Automatically generated, do not change]: > > > uname: SunOS silver 5.5.1 Generic_103640-39 sun4u sparc SUNW,Ultra-5_10 > > > compiler flags: gcc -g -O2 -Wall -Wno-implicit-int > > > > > > FVWM Version: 2.5.1 > > > FVWM_MODULEDIR: /u/phippst/sunos/libexec/fvwm/2.5.1 > > > FVWM_DATADIR: /u/phippst/sunos/share/fvwm > > > FVWM_USERDIR: /u/phippst/.fvwm > > > > > > Description: > > > When the pointer is on a tear off menu item fvwm stops processing > > > module messages. > > > > Yes, that's by design of the tear off menu code. I have no idea > > what to do about it (other that creating a separate instance of > > fvwm for each tear off menu). > > 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 funtion execution code needs (?) to grab the pointer too. 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]
