Hello Mark, > The typical way to stop a program that uses ooDialog is through > the cancel or ok buttons and let the ok() and cancel() methods > of the base class end the dialog.
Thank you, I found now that I have to add a '::method leaving' and there I may bring down all possible TCPIP sockets congruently waiting in blocking mode. Alas I have not found yet a way to 'force' the other thread. This must be possible from within the program because I may use Ctrl+C on the control window (with a socket command hanging in blocking mode I have to press it twice) and the program _is_ stopped. > Your case is complicated by the fact that you are starting > another thread in the dialog object that doesn't end. > Essentially what you need to do is write an ok() and a cancel() > method that over-rides the base class. In those methods, you > will need to signal your second thread to quit, wait for it to > quit, and then invoke the superclass method to close the dialog. Well, when I press OK or Cancle I do not want to wait for the second thread to quit, I want to force it as I don't mind what it does when me, myself and I hit QUIT! How may I rise a 'halt execution' or break or you-name-it to end at once? Best, M. -------------------------------------------- Kostenlose E-Mail-Adresse mit unbegrenztem Speicherplatz für E-Mails, Free SMS und OK-Drive, der Online-Festplatte. Sicher Dir jetzt Deine Wunschadresse @ OK.de: www.ok.de ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
