Re: crash when getting AppleScript dictionary
Re: crash when getting AppleScript dictionary
- Subject: Re: crash when getting AppleScript dictionary
- From: Christopher Corbell <email@hidden>
- Date: Thu, 6 Nov 2003 09:17:40 -0800
On Nov 6, 2003, at 8:30 AM, Don Briggs wrote:
Hi, Christopher
I suggest to visit
http://homepage.mac.com/donbriggs/
and download Suite Modeler
suite_modeler_2.2.dmg
(use the 2.2 version for Panther)
In free Demo mode, it can load your pair of plists.
You can browse your suite as a tree of table views.
The coloration of the cells will help show you what's default, OK, and
bogus.
(The coloration is controlled in the preferences panel.)
Use the "Find" panel to diagnose your suite.
There's on-line help in the app and some examples on the same page.
All best,
Don
On Nov 6, 2003, at 1:30 AM, Christopher Corbell wrote:
[....]
Can anyone suggest what in the world's going on here?
Even if I am missing some required field in the script suite
or terminology, I would hope that we could have graceful
failure from the Cocoa AppleScript code rather than a nasty
crash. Also, I checked my more complete suite (with just 1
class - the app - and 1 custom command, supported by the app)
in Suite Modeler demo, and didn't see any warnings - yet it
crashed as well...
Thanks for any help,
Christopher
Thanks Don -
As I mentioned in the previous post, I did try my
suite with the Suite Modeler demo and it did not indicate
the problem, or if it did I didn't know how to interpret
it (I didn't get any of the "error" colors in the UI,
but then I am partially color-blind :-| )
I finally found it (at least this first issue) - it
was the fact that the suite name in the .scriptSuite file
did not exactly match the namestem of the two
p-list (scriptSuite and scriptTerminology) files.
So I got it working after correcting this, but now as I
try to add some more sophisticated scriptable objects etc.
I'm getting the crash again.
I may purchase Suite Modeler to help develop my suites.
However I'm still troubled by the fact that this are
of system functionality will crash your application if
it gets subtly invalid property-list input. It feels
very brittle to me.
In addition to end-user features I'm designing some
suites for UI unit testing and automated black-box testing.
Now I'm kind of seeing that AppleScript itself could probably
use some unit testing. And in general for library design,
wouldn't an error code be nice thing to give an app instead
of EXC_BAD_ACCESS?
- Christopher
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.