Re: [twsocket] Asychronous opperation of Over Byte components -Automated processes

2011-02-16 Thread Francois PIETTE
How should one go about coding a user initiated automated/interactive processes which use TTnCnx and TTFtpClient? The user must be able to cancel the process and respond to prompts as required by the process. If one uses On... events to trigger the next step the code become part of the GUI and

Re: [twsocket] Asychronous opperation of Over Byte components-Automated processes

2011-02-16 Thread Brennan, Stephen
: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Francois PIETTE Sent: Wednesday, 16 February 2011 6:24 PM To: ICS support mailing Subject: Re: [twsocket] Asychronous opperation of Over Byte components-Automated processes How should one go about coding a user initiated

[twsocket] Asychronous opperation of Over Byte components - Automated processes

2011-02-15 Thread Brennan, Stephen
How should one go about coding a user initiated automated/interactive processes which use TTnCnx and TTFtpClient? The user must be able to cancel the process and respond to prompts as required by the process. If one uses On... events to trigger the next step the code become part of the GUI

Re: [twsocket] Asychronous opperation of Over Byte components - Automated processes

2011-02-15 Thread Brennan, Stephen
I will add that the wait process could simply be a periodic check (e.g FtpClient.State=ftpReady) amongst other code in the thread. Regards Stephen From: Stephen Sent: Wednesday, 16 February 2011 8:46 AM To: 'twsocket@elists.org' Subject: Asychronous opperation of Over Byte components -