Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU (Donna Converse)
Newsgroups: comp.windows.x
Subject: Re: drawing a window
Message-ID: <8904071415.AA01840@expo.lcs.mit.edu>
Date: 7 Apr 89 14:15:07 GMT
References: <1279@actnyc.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 16


>At this point I would expect to see the window.  It does not happen,
>however, until I click the mouse.  When I do so, it pops up anywhere,
>and then gets moved to where I want it.  The extra move I can deal with,
>but why do I need the click?

Ah, do you know about window managers?  The click is happening because
the window manager is allowing the user to place the window, using the
pointer cursor.  This happens as a result of your call to XMapWindow.

When you call XSetNormalHints, you can specify to the window manager
the programmer's idea of where the window should be.  Your call to
XMoveWindow is unnecessary, and it also causes the `extra move' that
you mention, and it is a very blunt method of placing a window on the
screen.  It does not follow conventions for bringing up windows, and
does not allow the user to indicate preference.