On 23:21 12 Aug 2002, Dominik Vogt <[EMAIL PROTECTED]> wrote: | On Mon, Aug 12, 2002 at 06:24:58PM +0100, John Latham wrote: | > This is not actually an undocumented feature change, but it is understated! | > :-) | > Fvwm 2.2.4 man page says: ``Fvwm remains fully functional during a wait.'' | > Fvwm 2.4.8 man page says ``Fvwm remains partially functional during a wait.'' [...] | > I spotted the one word difference after a few hours tracking down the cause of | > a very strange behaviour. Presumeably, you have optimised away some threads | > that had a memory/CPU overhead, and perhaps never imagined anybody would be | > using Wait in a clever (=stupid!) way. | > Alas, in AnotherLevelUp I was using Wait in a multi-threaded way, | | There is no multi threading in fvwm.
Hmm. But more than one active Wait is not an insane idea. | Event processing continues as usual. The modules can receive and | send data to and from fvwm, but fvwm ignores all module input | until the wait finishes. As this was the same in 2.2.x, I'm not | sure what was changed. In general: Wait + using modules = bad. On this kind of topic: what about a FvwmButtons Swallow whose client never appears? I'd imagine this is unrelated to FVWM itself and that the module is simply monitoring a stream of events from FVWM, or does the module get to preempty something off FVWM's event queue to do a swallow? Why do I ask? I swallow a wmflame in my button, but not on a VNC desktop (because it means constant VNC traffic, which I explcitly don't want). Now, instead of being smart and using piperead to conditionally generate the swallowing button, I always generate the button but conditionally fire up the wmflame. Is this likely to cause me trouble? It seems to work ok so far. -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ The Web site you seek cannot be located but endless others exist - Haiku Error Messages http://www.salonmagazine.com/21st/chal/1998/02/10chal2.html -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
