Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: dshr@eng.sun.COM (David Rosenthal)
Newsgroups: comp.windows.x
Subject: Re: dont resize, iconify, or move me
Message-ID: <9102072319.AA11252@devnull.Eng.Sun.COM>
Date: 7 Feb 91 23:07:30 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 31

Ken Lee writes:

> In article <38986@cup.portal.com>, DeadHead@cup.portal.com (Bruce M Ong) writes:
> |> 	I have an application that wants to tell the window manager
> |> to 1) not let the user resize it, 2) not let the user move it, and 3) not
> |> let the user to iconify it.
> 
> Check the override-redirect window attribute.
> 
And read the ICCCM,  sections 4.1.10, 4.2.2, and 4.2.9.  In general,
applications should *not* use override-redirect on their top-level
windows for the purposes you suggest,  only on pop-ups such as
warnings.

An application that has top-level non-pop-up windows that cannot be
resized,  moved and iconified is a very anti-social application
indeed.  The ICCCM is a set of rules that try to make applications
coexist with each other,  and this is why it deprecates things like
windows that cannot be resized,  moved or iconified.  There are
some applications whose job is to be anti-social,  like lockscreen.
Other than that,  you should take the time to be polite to the user
and allow them to decide whether they want the window to be
resized,  moved or iconified.  Anything less is simply rude.

If you really want to constrain the user's environment,  the right thing
to do isn't to try to fake out a general window manager.  It is to
run a window manager that provides the constrained environment to
applications that can also operate in the general environment (for
example,  when you as the developer are debugging them).

	David.