home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cbmvax!peter
- From: peter@cbmvax.commodore.com (Peter Cherna)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Locking Window Input -- How?
- Message-ID: <34822@cbmvax.commodore.com>
- Date: 2 Sep 92 13:36:50 GMT
- References: <302@nsq.uucp> <sysop.0csc@alphanet.alphanet.ch> <318@nsq.uucp>
- Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
- Organization: Commodore-Amiga, Inc. West Chester, PA.
- Lines: 25
-
- In article <318@nsq.uucp> entity@nsq.uucp (cybernetworx) writes:
- >Gee, thanks. You're so witty. If you didn't mean it as a joke, then the point
- >is that I need to keep all the other windows active. In any case, I've gotten
- >various replies to this, and I think I've got one that might actually do
- >exactly what I need. The basic idea is you take your current screen and save
- >all the IDCMP flags for all windows on that screen. Then you nullify their
- >IDCMP flags for the duration that my window is open and restore them when I
- >close my window. Of course I'll patch CloseWindow and CloseScreen to make
- >sure that nothing hokey happens by putting in my own additional checks.
-
- What you are doing is likely bad user-interface design, and certainly
- bad software design. You could create all kinds of potential problems
- by poking IDCMP flags, and it wouldn't even stop those windows from
- being activated.
-
- If you care to elaborate on the effect you wish to achieve, someone might
- help you with a system-friendly and user-friendly approach.
-
- Peter
- --
- Peter Cherna, User Interface Development Group, Commodore-Amiga, Inc.
- {uunet|rutgers}!cbmvax!peter peter@cbmvax.commodore.com
- My opinions do not necessarily represent the opinions of my employer.
- "I believe it's bad luck to be superstitious."
-
-