Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!euclid.jpl.nasa.gov!pjs
From: pjs@euclid.jpl.nasa.gov (Peter Scott)
Newsgroups: comp.windows.x.motif
Subject: Re: clientDecorations
Keywords: I want to take away from parent but not children.
Message-ID: <1990Dec7.191803.16448@elroy.jpl.nasa.gov>
Date: 7 Dec 90 19:18:03 GMT
References: <449@rruxc.UUCP> <1990Dec7.184609.7516@sctc.com>
Sender: news@elroy.jpl.nasa.gov (Usenet)
Reply-To: pjs@euclid.jpl.nasa.gov
Followup-To: comp.windows.x.motif
Organization: Jet Propulsion Laboratory, NASA/Caltech
Lines: 16
Nntp-Posting-Host: euclid.jpl.nasa.gov

>Getting rid of your frame all together 
>will solve the problem if you can do without it. I created a demo where I
>don't want the person running it to be able to moving the windows. At first
>I wanted the frame to have the frame title to show the user what the window 
>was, but I ended up getting rid of the frame and using an XmLabel to label 
>each of my windows. Having an XmLabel allowed me to select its color, font,
>etc... easily, and with no frame, the user can't move the window.

I defined a key binding in my .mwmrc to deal with windows that
I don't have decorated... it pops up the window menu so I can
select "Move".  I'd be interested to see a *really* foolproof
un-moveable window.

-- 
This is news.  This is your       |    Peter Scott, NASA/JPL/Caltech
brain on news.  Any questions?    |    (pjs@euclid.jpl.nasa.gov)