Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!wuarchive!uwm.edu!bionet!agate!saturn!ssyx.ucsc.edu!sirkm
From: sirkm@ssyx.ucsc.edu (Greg Anderson)
Newsgroups: comp.sys.mac.programmer
Subject: FilterProcs and global variables--I figured out a solution.
Message-ID: <10133@saturn.ucsc.edu>
Date: 27 Dec 89 22:37:05 GMT
Sender: usenet@saturn.ucsc.edu
Reply-To: sirkm@ssyx.ucsc.edu (Greg Anderson)
Organization: UC Santa Cruz; Division of Social Sciences
Lines: 12

In my last posting I was concerned about passing handles and all sorts
of useless things to a filterProc.  I just realized that the point is moot.

If my filterProc detects an event that would be difficult to interpret
(page up a scrolling field, for example), it simply returns with
itemHit = some very large & unique number.  My dialog handler takes care
of the details (since it has access to any global it might need).

  ___\    /___               Greg Anderson              ___\    /___ 
  \   \  /   /         Social Sciences Computing        \   \  /   /
   \  /\/\  /    University of California, Santa Cruz    \  /\/\  /
    \/    \/              sirkm@ssyx.ucsc.edu             \/    \/