Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!dat33228
From: dat33228@uxa.cso.uiuc.edu (Derek A. Taubert)
Newsgroups: comp.sys.apple2
Subject: Re: what to do with the Text Tools (was Re: FasText INIT)
Message-ID: <1991May23.183946.9465@ux1.cso.uiuc.edu>
Date: 23 May 91 18:39:46 GMT
References: <13749@pasteur.Berkeley.EDU> <11434@hub.ucsb.edu> <1991May21.054549.25355@ux1.cso.uiuc.edu> <53187@apple.Apple.COM> <1991May22.025850.9550@ux1.cso.uiuc.edu> <1991May22.095158.23187@nntp-server.caltech.edu> <1991May22.224402.12467@ux1.cso.uiuc.edu> <1991Ma
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 19

toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes:

>I suspect you're just pathologically worried about programs explicitly opening
>.CONSOLE so your speedy text routines won't have total control of the screen.
>I submit you're going to have to deal with this anyway so you're better off
>figuring out how to use the .CONSOLE driver to advantage rather than insisting
>on replacing it entirely!! Just what is it that you have to do that is so
>easily endangered by the console driver? If it's simply screen saving and
>restoring for process swaps, I don't see what the problem is.

Not quite.  Think about multiple processes running at the same time.  How do
you control who writes to the screen?  You patch the TextTools.

--
+ Derek Taubert --> derek@mrcnext.cso.uiuc.edu + Author of : GScii+	      +
+		    dat33228@uxa.cso.uiuc.edu  + and the world's most useless +
++++++++++++++++++++++++++++++++++++++++++++++++ desk accessory -> Amaze me   +
+ There are MOUSE technotes?    +  *******8-)  ++++++++++++++++++++++++++++++++
+ Ask me about my GS load meter +  ^^^^^^^^^^ Marge Simpson                   +