home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!swrinde!gatech!concert!samba!usenet
- From: Todd_Lewis@unc.edu (Todd M. Lewis)
- Subject: Re: Info about requesters and such
- Message-ID: <1992Nov23.154622.27015@samba.oit.unc.edu>
- Sender: usenet@samba.oit.unc.edu
- Nntp-Posting-Host: guitar.oit.unc.edu
- Organization: UNC Office of Information Technology
- References: <1992Nov23.103201.59188@qut.edu.au>
- Date: Mon, 23 Nov 1992 15:46:22 GMT
- Lines: 25
-
- In article <1992Nov23.103201.59188@qut.edu.au> barham@qut.edu.au writes:
- >Hello gurus,
- >
- >I have a question regarding Requesters, GadTools gadgets, ReqTools etc.
- >
- >[...]Now, while these "requester"[windows] are up, I want to block
- >all user input into the main window, and put up a wait pointer when the
- >main window is active.
- >Any ideas? Am I overlooking something entirely obvious?
-
- Just change the blocked window's pointer to some busy sign (like the watch
- on the Mac or the calender on Windows :-) and put a 1x1-pixel requester
- in the corner of the window. Change your IDCMP flags so messages don't
- pile up, and there you are. Not entirely obvious, but simple enough.
- You could get fancy and make your "requester" window active whenever
- your blocked window gets activated, but I don't think it's a good idea.
- Let the user activate whatever he chooses, I say.
-
- >| t.barham@qut.edu.au (Tim Barham) - "Dances with Mice" |
- Have a nice dance.
- --
- Todd M. Lewis / Todd_Lewis@unc.edu / utoddl@guitar.oit.unc.edu
- Another Month Ends / All Targets Met / All Systems Working / All Customers
- Satisfied / All Staff Eager and Enthusiastic / All Pigs Fed and Ready to Fly
-
-