home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!iggy.GW.Vitalink.COM!cs.widener.edu!dsinc!bagate!cbmvax!cbmehq!cbmfra!forgeas
- From: forgeas@swinjm.UUCP (Jean-Michel Forgeas)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Locking Window Input -- How?
- Message-ID: <PrNCr*oX1@swinjm.UUCP>
- Date: 4 Sep 92 12:26:27 GMT
- References: <34822@cbmvax.commodore.com> <paulk.1c1m@terapin.com>
- Reply-To: cbmvax!cbmehq!cbmfra!swinjm!forgeas (Jean-Michel Forgeas)
- Organization: The Software Winery
- Lines: 11
- X-Newsreader: Arn V1.00 alpha rel2
-
- In article <paulk.1c1m@terapin.com>, Paul Kienitz writes:
-
- > Probably the nearest thing to a friendly way to make sure no other
- > window activates when yours is active is to steal all the input with
- > an event handler until you want to let the system work normally again.
-
- This is totally bad application design.
- --
- Jean-Michel Forgeas uunet!cbmvax!cbmehq!cbmfra!swinjm!forgeas
- 4 rue du General Leclerc __
- 95210 Saint Gratien, France \/
-