Re: Error -609
Re: Error -609
- Subject: Re: Error -609
- From: Luther Fuller <email@hidden>
- Date: Sun, 10 Feb 2008 13:35:16 -0600
This morning, I posted Cubicles 1.0.1 to VersionTracker. A couple of
very minor changes. I didn't find anything that should cause the -609
error. All of the handlers, below, tell the Finder without error, so
the error is perhaps occurring at the beginning of tell Finder in the
main handler. So I swapped the last two lines so that 'path to ...'
is no longer inside the tell Finder block. Will this fix the problem?
We may never know!
on main()
set cubFol to my createCubicles()
set currentCube to my getCurrentCubicle(cubFol)
set nextCube to my chooseCubicle(cubFol, currentCube)
set deskFol to (path to desktop folder)
tell application "Finder"
On Feb 10, 2008, at 12:03 PM, Christopher Nebel wrote:
On Feb 8, 2008, at 5:40 AM, deivy petrescu wrote:
On Feb 8, 2008, at 8:36, Luther Fuller wrote:
Last week I wrote a relatively simple AppleScript application
that creates multiple, switchable desktops in Tiger (10.4.11 PPC
G4). (Something like Leopard's Spaces, but without a fancy GUI.)
This week I rounded-off the rough edges and fixed a bug.
Yesterday, I posted it to Version Tracker.
http://www.versiontracker.com/dyn/moreinfo/macosx/33917
I received a report from a user that he could not get it to run,
but instead got:
"Error = -609 Finder got an error: Connection is invalid." (My
error dialog.)
I'm not sure, but I don't think this is the kind of error I can fix.
I can't find additional info on this error at Apple's site.
Does anyone know more about the nature of this error?
Luther:
Error -609: "no user interaction allowed"
I don't know what reference you used to get that, but it's wrong.
-609 is "connection invalid", like deivy said; -1713 is "no user
interaction allowed." "Connection invalid" means that an
application you tried to talk to is dead; this sometimes happens
when you do something like this:
tell application "Finder"
quit
activate -- or any command, really.
end
There's a race condition, because "quit" returns before the process
is completely dead -- it still exists, but won't accept any more
events. (Yes, AppleScript could detect this error and retry, but
that creates an even more annoying problem.) The simplest (though
least efficient) solution is a short "delay" command; you can also
wait, testing to see if the application is still running, and
proceed once the answer is "no". This was discussed a month or two
back; check the archives.
--Chris Nebel
AppleScript Engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden