home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!malgudi.oar.net!hyperion!desire.wright.edu!rocker
- From: rocker@desire.wright.edu
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Re: 'model' window?
- Message-ID: <1992Dec17.084656.6252@desire.wright.edu>
- Date: 17 Dec 92 08:46:56 EST
- References: <1992Dec15.172737.6229@desire.wright.edu> <4748@execu.execu.com>
- Organization: Wright State University
- Lines: 21
-
- In article <4748@execu.execu.com>, kevin@execu.execu.com (Kevin English) writes:
- > In article <1992Dec15.172737.6229@desire.wright.edu>
- > rocker@desire.wright.edu writes:
- >>
- >> I have a window, actually as descendant of a fairly complex window,
- >>act like a dialog, ie. lock out all other windows and menuu, aka 'model', but
- >>not system model.
- >>
- >> I'm using TPW 1.0 (damm purchasing dept.) and OWL and any ideas are
- >>welcomed.
- >>
- >
- > Dave Edson wrote an excelent article in the Oct. Microsoft Systems
- > Journal : "Dave's Top Ten List of Tricks Hints, and Techniques for
- > Programming in Windows" - One of his tricks covered just this. In
- > summarry if you process the messages destined for this window with
- > IsDialogMessage() just as if the window were a modeless dialog, presto,
- > your window will have dialog like behavior.
-
- Am I missing somethine? How would IsDialogMesssage() lock out other
- windos?
-