Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!gatech!gitpyr!kpk
From: kpk@gitpyr.UUCP (Kevin P. Kleinfelter)
Newsgroups: net.micro,net.micro.pc
Subject: Re: Turbo Editor Toolbox
Message-ID: <1764@gitpyr.UUCP>
Date: Sat, 10-May-86 13:05:59 EDT
Article-I.D.: gitpyr.1764
Posted: Sat May 10 13:05:59 1986
Date-Received: Wed, 14-May-86 02:06:43 EDT
References: <1771@panda.UUCP> <2143@ism780c.UUCP> <4929@topaz.RUTGERS.EDU>
Organization: Georgia Institute of Technology
Lines: 19
Xref: linus net.micro:13241 net.micro.pc:7778

In article <4929@topaz.RUTGERS.EDU>, dpz@topaz.RUTGERS.EDU (David P. Zimmerman) writes:
> > In article <1771@panda.UUCP> plw@genrad.UUCP (Pete Williamson) writes:
> > >Does anybody have any experience using Borland's Turbo Editor Toolbox?
> > 
> > The Toolbox writes to the screen directly, which, if I'm not mistaken, puts
> > it in the class of programs that are not "well-behaved".  That might mean
> > problems if you want your editor to run under control of a system like
> > MicroSoft Windows, but I'm not sure about that.  Maybe someone who knows
> > more could comment?
> 
> Yes, it would cause problems.  Unless a non-Windows program is
> "well-behaved" (ie, doesn't write directly to the screen and doesn't
> read directly from the keyboard) it will not run optimally under
> Windows.  However, Windows can deal with these problem programs.
> 
Of course there is a simple fix to make Turbo Editor Toolbox work
as a well behaved program.  Since you have the source, modify it to
write using ANSI.SYS.  There is the minor problem that a screen update
will take about a week, though. :-)