home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!studly.mac.sas.com!Michael_Hecht
- From: Michael Hecht <Michael_Hecht@mac.sas.com>
- Subject: Distinguishing FrontClicks?
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <BzpzH1.8tD@unx.sas.com>
- X-Useragent: Nuntius v1.1.1d16
- Date: Wed, 23 Dec 1992 16:07:49 GMT
- X-Xxdate: Wed, 23 Dec 92 16:07:44 GMT
- X-Xxmessage-Id: <A75DF9007601050A@studly.mac.sas.com>
- Nntp-Posting-Host: studly.mac.sas.com
- Organization: SAS Institute Inc.
- Lines: 26
-
- Hello!
-
- I turned on the getFrontClicks bit in my SIZE resource, because it makes
- sense for my application. However, I don't want *all* parts of the window
- to respond to layer-changing clicks. How can I distinguish a click that
- changes my layer from other clicks?
-
- I can't just assume the next click after a resume event is a frontClick,
- since the user may have switched to me via the application menu or by
- double-clicking my Finder icon. For all I know, some other app may have
- called SetFrontProcess for me! Just throwing out the next click would
- probably frustrate the user (me) in these cases.
-
- The best method I could think of is to use EventAvail to look for
- mouseDown events in my resume event handler. If I see one I'll set a flag
- that I can look at in my mouseDown handler. Is this a reliable method?
-
- What I'd prefer is something along the lines of an event modifiers flag
- on the mouseDown that says "this event caused you to switch layers."
-
- Thanks!
- --Michael
-
- =======================================================================
- Michael P. Hecht | Internet: Michael_Hecht@mac.sas.com
- SAS Institute Inc.; Cary, NC USA | AppleLink: SAS.HECHT
-