Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!olivea!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Using the Layers library to do non-Intuition windows
Message-ID: <6504@amiga.UUCP>
Date: 22 Apr 91 17:48:23 GMT
References: <1991Apr19.003233.16889@netcom.COM> <20790@cbmvax.commodore.com>
Organization: I and I Computing, Palo Alto, CA
Lines: 30

(Peter Cherna) writes:
)(Ben Discoe) writes:
)>
)>  I'm working on a custom screen and I'd like to manipulate several
)>"text windows" without using real Intuition windows.  In fact, I am
)>trying to emulate the manner in which MSDOS applications allow
)>"windowing" on text-based screens.  I think the Layers library is
)>ideal for doing this?
)
)Yes it is.  You will be able to use it readily, if you keep Intuition
)out of your way.  Just keep in mind that you have to allocate your
)own screen-equivalent, and associate a Layer_Info with it.  Windows
)and requesters are built on Layer structures.  Window-functions
)have underlying layers versions, when applicable.

Intuition will probably get confused when the user clicks over a
non-Intuition layer.  Depends on which LayerInfo you use, I think:
Intuition's or your own.

Ben, you didn't mention why borderless Intuition windows wouldn't
work for you.  I'm not sure your comments on input redirection
were right on the mark, to the point of making it worthwhile to
try to go about your  project this way...

	jimm

-- 
--- opinions expressed herein are my own. ---
"... Because they can."
		- profound punchline to joke about dogs