On Tue, May 19, 2009 at 19:43, <jguyer@...> wrote:
> Actually, I wonder if there really is a 'tvea' AppleEvent. Both 'cppe'
> and 'tvea' seem like backwards (not byte-swapped) renditions of the
> more expected 'eppc' (kEventClassAppleEvent) and 'aevt'
> I note that 61657674 (not 616567674, which has a spurious 6 in the
> middle) is hex for 'aevt', an event class, which begs the question of
> what the event ID is. I wonder if "kHighlevelEvent 616567674 0000"
> means that a nonsensical 'aevt' '\0\0\0\0' event is being sent? Still
> leaves you wondering by who...
duh, of course, that makes more sense, thanks ;-), that old debug code
is all pre-intel transition (long gone by now FWIW, 8.4.7 is really
ancient for TkAqua).
the 61657674 is indeed just the same data (the EventRecord message) as
the 4-char code (just the message long cast to a string, hence the
endianness bug), and the 0000 is the event modifiers field: c.f. line
333ff of my tkMacOSXDebug.c link above
sprintf(buf, "%-16s %08x %04x %s", names->name, (int)
eventPtr->message, eventPtr->modifiers, cBuf);
i.e. no way to tell anything about the apple event causing the problem
from that debug message...
Kristoffer, as mentioned, you might want to ask the customers that see
this problem to turn on apple event logging... (ISTR there is a GUI
app for apple event logging around as well)
** Daniel A. Steffen **
** <mailto:das@...> **