Path: utzoo!mnetor!uunet!mcvax!botter!klipper!fons
From: fons@cs.vu.nl (Fons Botman)
Newsgroups: comp.sys.xerox
Subject: using TEdit
Message-ID: <969@klipper.cs.vu.nl>
Date: 13 Jan 88 10:58:10 GMT
References: <8801061910.AA23418@ucbvax.Berkeley.EDU>
Reply-To: fons@cs.vu.nl (Fons Botman)
Organization: VU Informatica, Amsterdam
Lines: 26

In article <8801061910.AA23418@ucbvax.Berkeley.EDU> 
ECOOPER@RCCA.BBN.COM (Eric Cooper x2947) writes:
>I posted this a couple weeks ago and have yet to receive a single response. 
>Surely someone must know something about using TEdit.  Please don't be shy.
>Thanks in advance.
>-----
>I am trying to use TEdit programmatically, but am finding it problematic.  
>My application will be sending a considerable amount of text to a TEdit 
>window. 

I have the same kind of problem. I have tried to use a TEdit window as a kind
of trace-window because important data tended to scroll off the window too
soon,  but I didn't get it working the way I would like it.  

I would like a single stream to write to. An optional maximum size of the
buffer contents like Texec.  Scrolling should be turned on and off using a
menu or be done only when the caret (at the bottom) is visible, this would
enable me to look at or copy other parts of the trace while the program is
running and generating trace output.  If scrolling occurs, then it should
scroll only one or a few lines at a time, to keep as much information as
possible in the window.  It may scroll more than one line to speed up
printing, as scrolling seems to be a slow operation.

Does some kind TEdit guru have a solution for these kind of problems?

						The Fons