home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!gatech!concert!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Opinion: What IBM should change in OS/2
- Message-ID: <1993Jan11.204420.28946@njitgw.njit.edu>
- Date: 11 Jan 93 20:44:20 GMT
- References: <1993Jan9.201238.17998@midway.uchicago.edu> <726705823snx@dashs.denver.co.us>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 21
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <726705823snx@dashs.denver.co.us> serls@dashs.denver.co.us (Dave Serls) writes:
- >A particular peeve:
- > I use quite a few windowed os/2 prompts. It would be nice to have
- >an option on the system menu, say 'exit', which unconditionally closes
- >a windowed prompt without the dialog box. I mean it's CMD.EXE running
- >there (unless you have one of the alternate commnad processors).
- >As an even better option or be able to assign the
- >'close' double-click to this 'exit' function.
-
- This dialog box is to protect you. Non-PM apps can't receive the
- WM_CLOSE/WM_QUIT message that OS/2 generates when forcing a session
- closed. This means that they can't clean themselves up. OS/2 can not
- clean up after them either - it must simply discard their memory and
- file handles. So, it asks if you're really sure. In any case, you
- shouldn't be quitting a DOS/OS/2 session that way - you should quit
- the app and let the session terminate itself.
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-