|
Mike, you can exit cleanly using escape messages (and monitoring for them!). By sending an escape message to a program higher up the stack, all intermediate programs are terminated. The problem is cleanup; if you need to do any special processing as the program exits, it's harder to do. I usually only use this technique for fatal errors; "top level" programs register themselves with a handler routine, and if a fatal error occurs an escape message is sent to the top level program. Joe
From: Mike I have just come into this new job and the screens I am working on, they pass a parameter back and forth to see if someone hit F3 (the standard exit key) and if they did, all programs in the stack exit out. While this does work, I am wondering if there is a better way. I am writting a new application and would like to see if there is a better way to do this.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.