Q: AppleScript is not recognizing Numbers in Mavericks

Have the same problem. My scripts stopped workgin after upgrade. Showing the same strange "classnames"

Same problem here as well.

It seems Numbers 3 does not come with an Applescript Dictionary so no scripts will work !

This will upset a lot of people I think.

May be you can use the previous version of the Numbers.

In my case, I updated to the Mavericks, and tried to updated the iWork, but my iWorks were in another folder, so instead Mavericks just downloaded anew the apps.

I think there is no any difference in the Numbers 2.3 and 3.0 except some missing features.

Would anybody try this theory and reply back?

(I'm just starting to learn AppleScript).

Thanks.

I don't think AppleScript is implemented, at least not yet, in Numbers 3.x. It doesn't show up in the Applescript Dictionary on my machine, although Numbers '09 still does.

If you want it (I do!) your giving feedback to Apple may help:

SG

This is causing me a major headache, two years ago when I first got an Apple I spent a lot of time writing an Applescript Routine which allowed me to reconcile my various bank statements against various accounts I keep a record of on my machine. Not only has this routine now stopped working as per original post but also my apple script is now full of all these <<class ###>> so even using Numbers 2.3 I am still getting the same problem.

To say I am not impressed is an understatement.

ElBeardo

According to this support document, AppleScript support (beyond the GUI-scripting common to all modern Mac applications) is coming to Numbers 3 sometime in the coming months.

Trust you keep backups of your scripts so you can just pull out a backup and keep working with Numbers 2.3 for now.

SG

I love how the support document says "Improvements to Applescript support."

Hi Rob,

Numbers 3.0, and indeed any modern application on the Mac, does support AppleScript to an extent. Numbers 3.0 allows AppleScript access to menu items, so you can do GUI scripting.  See this thread and this one too for recent examples with Numbers 3.0.

"Improvements to AppleScript support" probably means that it will once again be possible to "tell" objects within Numbers: documents, sheets, tables, cells. 

AppleScript support, of course, is not an "it supports/it doesn't support" dichotomy. It's a question of degree of support, how robust Numbers 3 "suite" in the AppleScript dictionary will be. Numbers 2.3 doesn't have extensive support, but it covers the basics.  Let's hope that the support in Numbers 3 will be as good or better.

SG

Saying use Numbers 2.3 is not as easy as it sounds as I have found out by experimentation over the last couple of days. I've tried saying these particular files should only be opened with Numbers 2.3 but if Numbers 3 is open it opens it in that anyway, so now I have to remember to ensure that I have quit Numbers3 and then "open with" Numbers 2.3.

I also discovered that the corruption of the Apple Script you have to be very careful how you open your script. Obviously if Numbers 3 is open then when you open your script it is corrupted but I also found that even if Numbers 3 is not open then again opening my script displays it corrupted. The only way I have found to be able to open my script without it being corrupted is to quit Numbers 3, open Numbers 2.3 and then open my script.

Just to rub salt into the wound I have now found that the new version of Pages has corrupted my templates.

One very unhappy man

ElBeardo

Yes, when using AppleScript with the old Numbers, best make sure Numbers 3.0 is closed.

Also you may do better if you rename the old Numbers to something like Numbers09 and in your AppleScript:

tell application "Numbers09"

SG