My experience with timers, they can start firing, or queuing up a massive succession. When I use them, I now disable them when entering, and re-enable on exit. If there are other data sessions involved in the application, make sure you call a user defined method of the timer object from the event. Your code for the timer should be in the user defined method.
HTH, Tracy -----Original Message----- From: Joe Yoder Sent: Friday, March 28, 2008 7:09 PM I modified some sample code that uses the Winsock control to allow continuously logging connection attempts to a remote server. I am using three different timers to update status, handle message delivery timeout, and to establish the rep rate. The code seems to work properly for a short time but before long the form starts responding to key or mouse clicks very sluggishly or not at all and I have trouble getting the form shutdown. Can someone give me some pointers about what to do and not do in a situation like this? Any debugging pointers? TIA - Joe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
