On Tue, Aug 13, 2002 at 10:32:41AM +1000, Cameron Simpson wrote:
> On 23:21 12 Aug 2002, Dominik Vogt <dominik.vogt_at_gmx.de> 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.
"Wait" works well only for windows that do appear do it fast. Any
other use is asking for trouble.
> | 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?
FvwmButtons just looks for a matching new window and otherwise
operates normally. But there is one important differene.
FvwmButtons doesn't care when the window appears, but with the
"Wait" command you explicitly ask not to continue executing the
function that triggered it. That is exactly what it is good for:
to not process any commands while the Wait is active.
> 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's safe to do that.
> It seems to work ok so far.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Aug 12 2002 - 20:07:24 BST