home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!qmw-dcs!jeremyr
- From: jeremyr@dcs.qmw.ac.uk (Jeremy Roussak)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Patching the _Launch Trap
- Message-ID: <1992Sep10.175427.5047@dcs.qmw.ac.uk>
- Date: 10 Sep 92 17:54:27 GMT
- References: <1992Sep8.024049.20121@Arco.COM> <abrn6k+.leonardr@netcom.com> <BuA3vu.97H@taligent.com> <1992Sep9.172136.13700@dcs.qmw.ac.uk> <BuCLzq.A7z@taligent.com>
- Sender: usenet@dcs.qmw.ac.uk (Usenet News System)
- Organization: Computer Science Dept, QMW, University of London
- Lines: 30
- Nntp-Posting-Host: sequent.dcs.qmw.ac.uk
-
- In <BuCLzq.A7z@taligent.com> keith@taligent.com (Keith Rollin) writes:
-
- >In article <1992Sep9.172136.13700@dcs.qmw.ac.uk>, jeremyr@dcs.qmw.ac.uk (Jeremy
- >Roussak) writes:
- >>
- >> The other problem with patching _InitGraf is that it doesn't
- >> move memory, so neither can (should) your patch. We won't get
- >> into the "all traps move memory because of patches" here! You
- >> can argue that unexpectedly moving memory within _InitGraf
- >> probably won't matter because of the way in which apps call it,
- >> but it's a little unsafe. _InitFonts, on the other hand, does
- >> move memory and is usually called immediately after _InitGraf.
-
- >You make a good point concerning patching _InitGraf. I had thought about it at
- >the time, but went ahead and patched it, figuring that I was safe for the
- >reasons you gave.
- >>
- >> When is _InitAllPacks called?
- >>
-
- >After your application is loaded, but just before its entry point is called.
-
- Are you sure this is correct? I just tried trapping with
- MacsBug on _InitAllPacks: the file dcmd fails to show that the
- application's resource file is open, CurMap is
- FinderPreferences and CurApRefNum is the Finder. (SE/30, 7.0
- tuned). If the app's resource file isn't available, it's tricky
- to find it's details. CurApName is correctly set up, though.
-
- Jeremy
-