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: '[email protected]' Subject: Asychronous opperation of Over Byte components - Automated processes 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 is basically a state machine. Do I have any other options with these components? Can the process be encapsulated in a thread instead where the thread can wait for each task to be completed or abort etc. before it moves on? Regards Stephen -- 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
