Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!ucbvax!bloom-beacon!eru!luth!sunic!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.UUCP (Michael van Elst)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Reading the keyboard without a window.
Keywords: keyboard,read,easy?
Message-ID: <553@mpirbn.UUCP>
Date: 13 Feb 90 09:56:20 GMT
References: <6675@ucdavis.ucdavis.edu> <131451@sun.Eng.Sun.COM> <6677@ucdavis.ucdavis.edu> <131573@sun.Eng.Sun.COM>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 20

In article <131573@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes:
>In article <6677@ucdavis.ucdavis.edu> (Brewski Rogers) writes:
>> Ah, but the problem is that I have a custom-copper list that's not connected
>> to a screen.(It intercepts <amiga>[m|n] to seem like a screen.) since there's
>> no screen, where would I put a window?
>
>The beauty of it is, that you don't need a real screen. You can open your
>borderless backdrop window in the workbench screen and make it the active
>window (use the ACTIVATE flag in the window struct).

If you use backdrop window on a public (WB) screen you have to intercept
mouse clicks too since you might hit another window that's in front of
the backdrop window.

Now, a 2 color, LORES, 10 rows high screen will use 400 bytes chip memory.
I don't think that it is too much memory wasted, if you attach your
borderless window onto this screen.

Michael van Elst
uunet!unido!mpirbn!p554mve