home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!wupost!cs.utexas.edu!sun-barr!ames!decwrl!sgi!cdp!jeff
- From: Jeff Dean <jeff@igc.org>
- Newsgroups: comp.os.ms-windows.programmer.misc
- Date: 21 Jul 92 00:15 PDT
- Subject: Re: Detecting when a WinExec'd prg term
- Sender: Notesfile to Usenet Gateway <notes@igc.org>
- Message-ID: <1668700005@igc.org>
- References: <18014.2a62f9a7@levels.unisa.edu.>
- Nf-ID: #R:18014.2a62f9a7@levels.unisa.edu.:-2126098115:cdp:1668700005:000:674
- Nf-From: cdp.UUCP!jeff Jul 21 00:15:00 1992
- Lines: 16
-
-
- >What do you mean unreliable? Do you mean that if I have a notifyregister
- >callback I don't have to let the message fall through to your program?
- >This would be very bad programming on somebody's part. On the other
- >hand I can always nuke your program with TerminateApp() and you
- >couldn't do anything about that either.
-
- The scenario goes like this: I want to WinExec another program, then
- be notified when it terminates. With NotifyRegister, if another
- program also requests notification, that program may catch the
- termination but not pass the information through, leaving me waiting
- for a notification that will never occur.
-
- Jeff Dean
- jeff@igc.org
-
-