Device: Pocket PC 2002, iPaq 3600
I have an RS232 sniffer application written using pure Win32 and is
streaming data into an Edit Control. The program runs well until the
Edit Control starts to become overwhelmed with too much data. I have
tested with various limits and at best, the control can handle ~8k of
text data before performance issues begin to degrade the application.
Anything above 32k and the Edit Control becomes unusable. I have
logic which looks at how much text has been inputed, and once the
limit is reached, I remove a 25% chunk from the beginning. So it
continuosly wraps the entire data stream. Everytime it does this
though, it uses too much processing time and performance suffers. So
that is why I am forced to limit it to a very small receive window
(~6k). But I would prefer to store more.
I am also using SetDrawupdate to only update the Edit Control *after*
the data has been inputed, and am calling the correct messages to
accomplish the rest. Needless to say, the control is very slow to
respond with too much data in it (~36k), and I believe I lose some of
my streaming in the process.
I can subclass the edit control but don't know what I can perform to
speed up and relieve some of the handling of displaying the data. My
preferred operation would be simply a single low-level call that
appends new data to the end of the edit control. No multiple redraws,
replace selections, or other crap.
Apart from writing my own Edit Control (which I *really* don't want to
do), are there other methods to improve the standard Edit Control
performance? Some subclassing tips/tricks/hacks, anything that would
improve its response time and allow it to handle more data more
efficiently?
Sebastian "Suffering with Edit Controls" Dwornik