Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!mcvax!kth!sunic!chalmers!tekno.chalmers.se!d83_sven_a
From: d83_sven_a@tekno.chalmers.se (Sven (Sciz) Axelsson)
Newsgroups: comp.sys.mac.programmer
Subject: MacroMaker does strange things to the system...
Message-ID: <789@tekno.chalmers.se>
Date: 24 May 89 22:32:09 GMT
Organization: Chalmers Univ. of Technology, Gothenburg, Sweden
Lines: 26

I've spent most of the day tearing my hair in dispair for a - thought I -
utterly unbelievable bug. This was not so, however...

THE SCENARIO: I am hacking on a DA which will utilize the journaling mechanism.
Today I pulled all parts together and everything ought to work just fine...
I compile etc. and open the DA - it runs wild. It is receiving jRecordCtl calls
all the time although I can see with MacsBug that JournalFlag is definitely
zero. Huh, what, and why?? After several hours of fruitless search for some
bug in my program I realized - MacroMaker! Throw MacroMaker out and - low and
behold - now it works perfectly.

QUESTION: Why is it that Apples own programs always breaks all Apples own
programming guidelines? Other macromaking utilities (such as QuicKeys) can
manage without disrupting the journaling mechanism.

UNRELATED QUESTION: The reason for me using MacroMaker instead of QuicKeys in
the first place was that I couldn't get QuicKeys to define a macro in the
DA-Handler layer only (MacroMaker can do this). Is there a way to do this
with QuicKeys that I've missed?

+-------------------------+--------------------------------+------------------+
|   Sven Axelsson         |  d83_sven_a@tekno.chalmers.se  |  DISCLAIMER:     |
|   dep:t of Linguistics  |          (^^ best ^^)          |                  |
|   univ. of Gothenburg   |        dlv_sa@hum.gu.se        |  This is not     |
|   SWEDEN                |      usdsa@seguc21.bitnet      |  a disclaimer.   |
+-------------------------+--------------------------------+------------------+