🚀 go-pugleaf

In article <2214@helios.ee.lbl.gov> beard@ux3.lbl.gov (Patrick C Beard) writes:
>I am writing an application which contains a "welcome" screen.  I would like
>this window to occupy the entire Mac+ screen, but I can not get rid of the
>blank menu bar which is occupying 20 pixels at the top of the screen.

>In article <3858@emory.mathcs.emory.edu>, I wrote:
> It *is* possible to cover the entire screen, including the menu bar, by simply
> redefining the variable GrayRgn, which defines the region where windows can be
> drawn.

In article <11118@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:
>	Although this will work, Apple has said before that the GrayRgn is
>READONLY!  You are NOT to modify it! Especially under MF this is an even BIGGER
>no-no since you are doing this behind the back of other apps and the GrayRgn
>is a LMGlobal and the effect is VERY interesting.

I imagine this prohibition is in the tech notes, since it isn't mentioned in
Inside Mac where GrayRgn is defined.  I defer to Leonard's vastly greater
wisdom.  Now if he had just given *his* solution to this problem.  (I only
provided mine because no one else seemed to be volunteering the information.)

It has also been pointed out to me by others that the method I provided would
not work with multiple monitors, since screenBits.bounds only describes the
main screen.  If you like to play with fire, you might redefine GrayRgn to be
its bounding box; this will give you a rectangle which will be sure to include
all monitors.  To ensure that you include the menubar, also, this rectangle
should contain screenBits.bounds.

*
  *      **                  Scott Robert Anderson      gatech!emoryu1!phssra
   *   *    *    **          phssra@unix.cc.emory.edu   phssra@emoryu1.bitnet
    * *      * *    * **
     *        *      *  * * * * * * * * * * * * * * * * * * * * * * * * * * * *