When the debugger is attached is it exactly the same like when it's not
attached for the program being executed ?
I would say no since my application is working.
But I would say it doesn't change the time required to do domething.
OK then, my idea was that it's different.
Actually I work with some external hardware devices (USB / serial
connected) that sometimes in the past performed like in the reported
problem and the solution was to give some more available time to the
program with Application.ProcessMessages. But when the debugger was
attached, this solution was not needed and it always worked fine.
Anyway, my approach for the specific problem reported is more generic,
not dealing at winsock level.
OK, thanks anyway.
--
francois.pie...@overbyte.be
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
