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? To retain compatibility, there could be commands like this: OnCommand Popup SendToModule FvwmMenu P $* OnCommand Menu SendToModule FvwmMenu M $* OnCommand AddToMenu SendToModule FvwmMenu A $* OnCommand DestroyMenu SendToModule FvwmMenu D $* # Make "SendToModule Module" load FvwmMenu, LoadOnDemand FvwmMenu The first time fvwm encountered a "SendToModule" for a LoadOnDemand module, it would load it. As long as the module stays loaded, the menus should be fast enough. -- Dan Espen E-mail: [EMAIL PROTECTED] 444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570 Piscataway, NJ 08854 -- 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]
