Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!jato!vsnyder
From: vsnyder@jato.jpl.nasa.gov (Van Snyder)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Windows and Events Questions
Message-ID: <1991Apr22.072944.1120@jato.jpl.nasa.gov>
Date: 22 Apr 91 07:29:44 GMT
Reply-To: vsnyder@jato.Jpl.Nasa.Gov (Van Snyder)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 31

In ONE of several similarly designed programs, the name and info lines
of windows get crud when another window is topped, e.g. Control Panel.
I remember reading something to be careful about with these data, but
I'll be damned if I can find it again!  I was careful to make both of
them static (non-stack) strings.  Does anybody remember what to do so
this doesn't happen?

If I create a window with WindowCreate(...Closer+InfoLine+Name...), then
do WindowSet(...Closer+Name...) and then WindowGet(...WorkXYWH,x,y,w,h),
the rectangle that comes back is as though the InfoLine were still there.
The picture on the screen, and the behaviour when redrawing or topping
verifies this.  Is there a way to make the InfoLine temporarily go away,
or must one destroy the window and re-create it?

When window B is atop window A, and window B is moved, window A is told
to redraw everything of it that shows.  How can one repaint just those
parts that are newly exposed?  It's not too hard when dealing only with
windows the program owns, but what about DA windows?

How can one wait for left OR right mouse button with Event<...>?
EventButton and EventMultiple wait for left AND right mouse button down
if the mask and button arguments are both 3.

Any help, on any question, would be appreciated.  To ensure me receiving
it, please e-mail answers.  Of course, if you think others will be
interested, post also.

-- 
vsnyder@jato.Jpl.Nasa.Gov
ames!elroy!jato!vsnyder
vsnyder@jato.uucp