FVWM: FVWM requires mouse-move to finish starting up?

From: Fuzzy Fox <fox_at_foxtaur.com>
Date: Sat, 17 Jul 1999 15:07:17 -0500

I decided to change around some of my X startup stuff, and found a
strange behavior of fvwm2.

Previously I would start all my clients from my .xsession script, and
then exec fvwm2 at the bottom. Now my script basically just exec's
fvwm2, and I've moved my clients' startup to the InitFunction, like so:

    AddToFunc InitFunction
    + "I" Exec xload
    + "I" Exec oclock
    + "I" Exec xcb
    + "I" Exec netscape -iconic
    + "I" Function StandardXterms
    + "I" Exec ICQ

Strangely, though, when I start up my X session now, I am treated to a
completely blank X screen, and it will stay that way, indefinitely,
until I touch the mouse, moving it slightly. Then the window manager
"wakes up" and runs its InitFunction.

Why does it do this?

-- 
   fox_at_dallas.net (Fuzzy Fox)      || "Nothing takes the taste out of peanut
sometimes known as David DeSimone  ||  butter quite like unrequited love."
  http://www.dallas.net/~fox/      ||                       -- Charlie Brown
--
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 Sat Jul 17 1999 - 15:08:29 BST