Change in debugging command "log"?
Change in debugging command "log"?
- Subject: Change in debugging command "log"?
- From: Gil Dawson <email@hidden>
- Date: Mon, 20 Sep 2004 04:16:20 -0700
Hello--
I have been writing scripts using the Classic Script Editor v 1.8.3
for some time. Today I started to use the OS X Script Editor v 2.0
and found a difference that really confuses me. Maybe you have found
how to get the same thing or something similar to work in OS X...
could you please let me know?
In both Script Editors, the Event Log window will show either Events,
or Events and Results, or neither.
In the "Neither" mode, the OS 9 Script editor will still show the
output of the "log <string>" commands anyway. Therefore, peppering a
new script with "log" commands was a handy way to watch things work,
and you could adjust the verbosity by commenting out -- or adding --
log commands as you pleased.
Now comes Mac OS X Script Editor, and it appears that "Neither" mode
has been changed to "Nothing" mode, and it really means that nothing
is logged. You can still see the output from "log <string>"
commands, but now you must turn on Event Logging to see them. This
means that your debugging messages will be embedded in the torrent of
Events -- what a mess!
Has anyone developed a workaround for this problem? Maybe you have
developed a better way to present debug messages to yourself?
I'd appreciate hearing your thoughts.
--Gil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden