Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!uwvax!puff!avery
From: avery@puff.WISC.EDU (Aaron Avery)
Newsgroups: comp.sys.amiga
Subject: Re: Custom screen's SCREENQUIET flag
Message-ID: <795@puff.WISC.EDU>
Date: Tue, 9-Jun-87 11:11:05 EDT
Article-I.D.: puff.795
Posted: Tue Jun  9 11:11:05 1987
Date-Received: Fri, 12-Jun-87 02:53:32 EDT
References: <8706090257.AA22852@cory.Berkeley.EDU>
Organization: U of Wisconsin CS Dept
Lines: 25
Summary: Well, almost...

In article <8706090257.AA22852@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> 
> 	Adding to the discussion of features unknown and unused:
> 
> 1.2 Supports several new flags for openning screens.  One of these is 
> called SCREENQUIET, another is called SCREENBEHIND.  SCREENQUIET allows
> for all the normal screen gadgetry at the top, but makes it invisible so
> you can still manipulate the screen memory directly without intuition screwing
> you up!!
>
I do use it in my application. It works fine for having a window and screen
sharing memory. If you have the window covering up the screen's title bar,
normally, (w/o SCREENQUIET) when you hit the menu button, the screen's title
will be rendered into its bitmap. This problem is fixed with SCREENQUIET.
However, if you have a window and screen sharing display memory, and you
let the screen's title bar show on top of the window, hitting the menu button
will still cause rendering to stay in the display. To fix the problem of not
being able to push the screen to the back, I hooked a couple of invisible
boolean gadgets to my window in the appropriate places and call ScreenToBack()
and ScreenToFront() when they're hit. You still can't drag it down, but if
you want the workbench and it (a terminal program) on the display at the same
time, you can drag the workbench down.

Aaron Avery ({seismo,caip,allegra,harvard,ihnp4}!uwvax!puff!avery)
	    (avery@puff.wisc.edu)