Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: front/back gadget and WindowToFront
Message-ID: <22524@cbmvax.commodore.com>
Date: 17 Jun 91 23:28:42 GMT
References: <1991Jun16.164922.15206@ucunix.san.uc.edu>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Distribution: usa
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 28

In article <1991Jun16.164922.15206@ucunix.san.uc.edu> link@ucunix.san.uc.edu (Virginia Link) writes:
>Is there a varibale that stores the front window for each screen
>that I can change back to the window value after I call window
>to front for the clock window.

No.  The window list in the Screen structure determines the window
ordering, and it's read-only.  The best thing is to use shift-click
on the depth gadget, which forces a window to the back.  I would
like to add a fix to Intuition that would make non-frontmost
fully-exposed windows go to the back, instead of to the front,
when you click on their depth gadget.

>By the way, why is calling UpFrontLayer not legal on this screen ?

Layers is an underlying engine for window-like operations.  Intuition
owns the screen, and brings each layers operation out in a Window...()
form.  You must use the Window...() form (WindowToFront(), in this case)
to keep Intuition in the loop.  It owns the screen, and needs to know
what transpires there.

>vl

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Gosh, didn't he have anything positive to say at all?"