Re: Protocol log capture?

"Roger Binns" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <000a01c50f33$ff88eec0$3501a8c0@rogersqyvr14d3>
> I'm still having spotty success getting the GUI to play nice with viewing
> the protocol log on Mac OS X.  I'm getting closer on the VX6100 index
> resolutions, and was wondering if the protocol log is actually written to a
> file so that I don't have to wait through the 1-second per line scroll speed
> in the protocol log viewer.

It isn't written to a file.  The data comes from the comms thread and in
the main thread is added to a cStringIO.  An idle handler in the main
thread then appends the text to the log text control.  The wxWidgets
API provides methods that work on lines within the text.  The underlying
native widgets don't.  In many cases they don't actually have an append
method either.  So wxWidgets reparses *all* the text, not just the new
text, in order to find each end of line.

That all makes it go slower and slower and slower ...

I'll look into also dumping to a file.

Roger


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.