Indy Telnet SendString robustness best practice


I have a simple Firemonkey application with a series of buttons and sliders (track bar) that when a user interacts with these controls it send a command using IdTelnet. i.e.

IdTelnet1.SendString(‘ ‘+str+#13);

The problem is that very occasionally the users experience total lockup of the app and windows reports the app as “Not responding” when clicking on something. I have not reproduced this myself however I suspect its related to clicking on buttons in quick succession.

My current theory is that I am getting re-entry into SendString and IdTelnet is not handling this well.

Before jumping into writing a queued sending system I wanted to ask for any best practice advice. Is this a known issue and what is the best way to do quick fire sends that are user initiated?

Comments are closed.