Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!think!ames!oliveb!sun!pepper!cmcmanis From: cmcmanis%pepper@Sun.COM (Chuck McManis) Newsgroups: comp.sys.amiga Subject: Re: Odd question Message-ID: <23916@sun.uucp> Date: Tue, 21-Jul-87 15:35:43 EDT Article-I.D.: sun.23916 Posted: Tue Jul 21 15:35:43 1987 Date-Received: Thu, 23-Jul-87 04:45:46 EDT References: <3947@spool.WISC.EDU> Sender: news@sun.uucp Reply-To: cmcmanis@sun.UUCP (Chuck McManis) Distribution: comp Organization: Sun Microsystems, Mountain View Lines: 16 In article <3947@spool.WISC.EDU> derek@speedy.WISC.EDU (Derek Zahn) writes: .>Does anybody know the details about how console windows actually render their .>text? In particular, I was wondering if it might be possible to use .>SetFunction() to intercept the call that puts out the text to my CLI. .>My reasons for this are several and rather obscure. I thought at first .>that at the lowest level, Text() must be used, but haven't had any luck .>with that approach. Maybe I am just doing it incorrectly? Yes, this is exactly what it does. What Fast Fonts (a product of Microsmiths) does is replace the Text() function with one that is quite a bit faster. Thus anything that uses a CLI (or the console device) will render it's text to the screen more efficiently. So yes, replacing Text() should do what you want. --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses, but you knew that didn't you.