Elad Eyal <elad_at_CS.bgu.ac.il> writes:
> Good morning,
>
> Is there any way to know when fvwm is 'busy' and when it's 'idle'.
> Suppose I want to display a rubberband over the screen. If I want fvwm to
> iconify a window, I'll need to hide the rubberband while it does it, and
> redisplay it after it's done. Currently I have there a
> sleep_a_little(150000) which is almost too slow to be bareable, but this
> is obviously not the best solution. The problem is that I paint the
> rubberband with XDrawRectangle directly over root, and not in a window of
> itself, ergo problems with window which overlap.
>
> http://www.cs.bgu.ac.il/~elad/GEOM.tgz
> _
> (_ / _ / ( E-mail pigeons nest in binary trees )
> (__/__(/\_(/ http://www.cs.bgu.ac.il/~elad
>
>
Fvwm really needs the ability to do synchronization with modules in this
fashion. I had similar problems with FvwmIconMan when the user would use fvwm
to move my icon manager window. This is a complicated problem. My hope is that
after fvwm2 is officially released we can redo the module interface to allow
for tighter integration on such things.
None of that helps you though. I gather that your problem is just that while
rubberbanding, you send a command to fvwm to unmap a window. It's not that
fvwm is doing other things behind your back.
If so, then it shouldn't be too hard to add a new message type to handle
this. When a module sends a command to fvwm to execute, fvwm sends back a
packet when that command is completed. It seems that we would just have to
send that message back after the call to ExecuteFunction() in
HandleModuleInput() in module.c. Wouldn't be hard at all. And since your
module would be the only one using it for now, it shouldn't be a risky thing
to add.
It seems a reasonable thing to add. If a module wants fvwm to do something, it
should be able to know when it's done.
Now if you are worried about fvwm doing things that your module has no way of
knowing about, the only way to cleanly handle that is to add semaphores to
fvwm. The odds of that happening are probably fairly slim, and easily
controlled by the user (I quit netscape, which takes 20 seconds to actually
quit, and in the meantime start resizing windows. I should just know better).
--
Brady Montz
bradym_at_cs.arizona.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Aug 19 1997 - 15:29:50 BST