Protocol tracer: high performance output
-
Hello all, I've to rebuild a 'analyser' to a MDI application on which each doc/view output is generated, and sometimes very fast and a lot. Each doc/view has it's own socket-connection to external equipment. These equipment produces sometimes a lot of 'debugging' information, which is displayed in the doc/view. The communication is via UDP/IP and a fixed protocol using a form of windowing is used. My problems/questions --------------------- 1. What kind of control is most reliable for fast writing and deleting lines for displaying by the application itself: CEdit or CList (or other control which has past CodeProject). Deleting is required, since we only want to keep x-amount of lines available (preventing memory eating). 2. What is the best way of architecture to implement this, refering on fast handling and MDI? No user-input is required, only initially to setup the connection. Of course: when a lot of data is being dumped, the controls to buttons for: End Connection, exit application etc has to be remain a bit responsive. That is already a problem in the current application... Thanks in advance, EiSl
-
Hello all, I've to rebuild a 'analyser' to a MDI application on which each doc/view output is generated, and sometimes very fast and a lot. Each doc/view has it's own socket-connection to external equipment. These equipment produces sometimes a lot of 'debugging' information, which is displayed in the doc/view. The communication is via UDP/IP and a fixed protocol using a form of windowing is used. My problems/questions --------------------- 1. What kind of control is most reliable for fast writing and deleting lines for displaying by the application itself: CEdit or CList (or other control which has past CodeProject). Deleting is required, since we only want to keep x-amount of lines available (preventing memory eating). 2. What is the best way of architecture to implement this, refering on fast handling and MDI? No user-input is required, only initially to setup the connection. Of course: when a lot of data is being dumped, the controls to buttons for: End Connection, exit application etc has to be remain a bit responsive. That is already a problem in the current application... Thanks in advance, EiSl
> 1. What kind of control is most reliable for fast writing and > deleting lines for displaying by the application itself: CEdit > or CList CListCtrl is much easier to use when you want to insert/delete lines. Also, CEdit has serious capacity limitations on Win9x - don't know how much it affects you. Are you just putting the information on the screen, or also store it somewhere else in your program for statistics/detailed info etc.? If yes, you can consider using LVS_OWNERDATA style for your list control. Tomasz Sowinski -- http://www.shooltz.com.pl