Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!think!samsung!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!rogers From: rogers@iris.ucdavis.edu (Brewski Rogers) Newsgroups: comp.sys.amiga.tech Subject: Re: Reading the keyboard without a window. Keywords: keyboard,read,easy? Message-ID: <6677@ucdavis.ucdavis.edu> Date: 8 Feb 90 23:54:32 GMT References: <6675@ucdavis.ucdavis.edu> <131451@sun.Eng.Sun.COM> Sender: uucp@ucdavis.ucdavis.edu Reply-To: rogers@iris.ucdavis.edu (Brewski Rogers) Organization: U.C. Davis - Department of Electrical Engineering and Computer Science Lines: 17 In article <131451@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes: >Sometimes it is useful to have intuition just provide the input for you, >in which case the borderless backdrop approach works well. It doesn't >take up hardly any memory (just the sizeof(struct Window)). > >--Chuck McManis >uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@Eng.Sun.COM Ah, but the problem is that I have a custom-copper list that's not connected to a screen.(It intercepts [m|n] to seem like a screen.) since there's no screen, where would I put a window? ------------------------------------------------------ Quantum _\/_ 2727 Eel Bruce (6502 RULES!) Rogers |\ Duck ( 0 0) Davis, Ca 95616 Quantum Duck Software, |\ \______/ / \\\ 916-756-2684 rogers@iris.ucdavis.edu |\ < < | \/ "My brain is on fire!" \________/ Quark!