Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!rutgers!att!ttrdc!ttrde!ttrdf!fjo
From: fjo@ttrdf.UUCP (Frank Owen )
Newsgroups: comp.sys.mac.programmer
Subject: Multifinder: how do I patch GetNextEvent?
Message-ID: <747@ttrdf.UUCP>
Date: 7 Oct 88 16:06:09 GMT
Organization: AT&T, Skokie, IL
Lines: 32


   What is the proper way to patch the GetNextEvent() trap for
compatibility with MultiFinder?.  I have created an INIT that
patches this call. The first thing that the patch does is call the
old GetNextEvent, (the one that was there at INIT time.). 
The purpose of the patch is to translate the CapsLock modifier into
the command-key modifier.
   My patch still seems to be in there (the desired result occurs), but 
it introduces long delays and curious behaviour when running under MultiFinder. 
The two specific weird things are :
   1) If I have the Finder as the top window, and then obscure an icon on
      the desktop, then expose it again, the icon  does NOT get redrawn until
      it gets selected again.
   2) While running LightSpeed C's debugger, if I enter an expression in the
      Data window, the watch cursor comes up, and stays there forever,
      UNTIL you mouse-down a few times on another application's window.
      Then when you re-activate the debugger window the expresion in the
      data window is correctly evaluated and displayed.

  I am running from System Tools 5.0. (The first official Multifinder).
All above behaviour ceases if I either remove my INIT, or run without
MultiFinder.

Any ideas?

Frank Owen (..!att!ttrdf!fjo)

-- 
Frank Owen (fjo@ttrdf)  312-982-2182
AT&T Bell Laboratories 
5555 Touhy Ave., Skokie, IL  60077
PATH:  ...!att!ttrdf!fjo