Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!nntpd.lkg.dec.com!afire!usenet
From: schoeller@clt.enet.dec.com (Dick Schoeller)
Newsgroups: comp.windows.x
Subject: Re:  Which window manager is up?
Message-ID: <1991Jun25.132406.17208@afire.zko.dec.com>
Date: 25 Jun 91 13:24:06 GMT
References: <9106210623.AA06713@lightning.McRCIM.McGill.EDU>
Sender: usenet@afire.zko.dec.com (USENET News System)
Reply-To: schoeller@clt.enet.dec.com (Dick Schoeller)
Organization: Digital Equipment Corporation, Nausea, Cow Hampshire
Lines: 25

In article <9106210623.AA06713@lightning.McRCIM.McGill.EDU>, mouse@lightning.mcrcim.mcgill.EDU (der Mouse) writes:
|> Some or all of those may provide some way to guess whether the WM is
|> running or not, but any such way can make mistakes (I feel sure
|> XmIsMwmRunning, for example, can be fooled).
|> 
|> Why do you care?  You shouldn't care what window manager is running; if
|> you think you do you are probably trying to solve the wrong problem.
-----

Sure, XmIsMotifWMRunning can be fooled.  All you have to do is make your
window manager do the same things mwm does.

Checking for window manager running is less important now that most window
managers are ICCCM compliant.  As long as you aren't trying to do wm specific
stuff, you shouldn't care.  However, if you are expecting to run in an
environment where a substantial number of users may be using a non-ICCCM
window manager (ie: dxwm), then you may want to do some checking in order
to determine which method to use for some operations such as iconification
or changing the icon pixmap or using the iconify pixmap field in DEC_WM_HINTS.

Dick Schoeller                  | schoeller@clt.enet.dec.com
Digital Equipment Corporation   | 603-881-2965
110 Spit Brook Rd., ZKO2-3/R56  | "Either Judaism has something to say to the
Nashua, NH 03062-2642           | world or it has nothing to say to Jews."
                                |                             - Dennis Prager