• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?


  • Subject: Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?
  • From: "koenig.yvan" <email@hidden>
  • Date: Sun, 16 Feb 2014 10:51:34 +0100


Le 15/02/2014 à 22:53, Bryan Harris <email@hidden> a écrit :


On Feb 15, 2014, at 9:04 AM, Deivy Petrescu <email@hidden> wrote:
On Feb 15, 2014, at 04:19 , koenig.yvan <email@hidden> wrote:
Le 15/02/2014 à 05:32, 2551 <email@hidden> a écrit :
On 15 Feb 2014, at 04:03, Deivy Petrescu <email@hidden> wrote:
With TextWrangler 4.5.6 it failed.
Yvan KOENIG (VALLAURIS, France) vendredi 14 février 2014 21:37:25

Thanks.
Very interestingly, in BBEdit works flawlessly.
May be we can shoot an email to the people at BareBones.

Well, it works for me with TextWrangler 4.5.6 on 10.9.1.

tell application "TextWrangler"
display dialog (get ID) giving up after 5
end tell

Replies:
tell application "TextWrangler"
display dialog "com.barebones.textwrangler" giving up after 5
--> {button returned:"OK", gave up:false}
end tell
Result:
{button returned:"OK", gave up:false}

I got this log report

tell application "TextWrangler"
activate
display dialog "com.barebones.textwrangler" giving up after 5
--> error number -1708
«event ascrgdut»
--> error number -1708
display dialog "com.barebones.textwrangler" giving up after 5
Résultat :
error "Erreur dans TextWrangler : Délai dépassé pour un AppleEvent." number -1712


I thought that the French System may be the problem.
But there is an other hypothesis : I'm running the version available thru App Store which is slightly different from the one available directly from BareBones.


Yvan,
I also see that you get the 

--> error number -1708

while Phil (and I) do not.
Could it be the French OS?

I installed TextWrangler from the App Store and I get the same -1708 error after I press the OK button on the dialog.  I also waited five seconds but nothing happened (not sure what is supposed to happen after five seconds).

With English selected in System Preferences:

TextWrangler got an error: Can’t continue «event ascrgdut».

With French selected in System Preferences:

Erreur dans TextWrangler : Il est impossible de poursuivre «event ascrgdut».

V/r,
Bryan

When the giving after instruction is correctly treated we are supposed to get :
display dialog "com.apple.iWork.Pages" giving up after 5
--> {button returned:"", gave up:true}
which means that we didn't pressed a button during the defined time duration.

When the instruction is wrongly treated — in fact not treated at all — here, the dialog is displayed for a long time and the script fails with the error :
error "Erreur dans wxyz : Délai dépassé pour un AppleEvent." number -1712


I made an other test with :
tell application "Pages"
get id
tell me to display dialog result giving up after 5
say "passed"
end tell

Logically, the errors linked to display dialog don't strike.
But, as say is a Standard Additions feature it issue them.
tell application "AppleScript Editor"
display dialog "com.apple.iWork.Pages" giving up after 5
--> {button returned:"", gave up:true}
end tell
tell application "Pages"
say "passed"
--> error number -1708
«event ascrgdut»
--> error number -1708
say "passed"
--> error number -10004
end tell
tell current application
say "passed"
end tell


If I run the script a second time, only the error -10004 is issued.
I forgot to write that when a script is run several times, in Pages, there is no error issued after display dialog
To get rid of them, one more time « tell me to » is the correct weapon.

tell application "Pages"
get id
tell me to display dialog result giving up after 5
tell me to say "passed"
end tell

gave this log report :

tell application "AppleScript Editor"
display dialog "com.apple.iWork.Pages" giving up after 5
--> {button returned:"", gave up:true}
end tell
tell current application
say "passed"
end tell


Mail behave exactly the same way .
At first execution, display dialog issue the two errors -1708 but no error -10004
say issue error -10004

If we run again, only say issue an error.

As I always got this behavior, I was not surprised.

I will mad tests running the system in English for see.
If I don't get the errors, I will file a report.
I guess that it means that one string is localized which was supposed to stay in English.
I didn't saw that since the Apple //gs era.

Yvan KOENIG (VALLAURIS, France) dimanche 16 février 2014 10:51:09


 _______________________________________________
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

References: 
 >Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: James Gretton <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Christopher Stone <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: James Gretton <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Christopher Stone <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Deivy Petrescu <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Deivy Petrescu <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Deivy Petrescu <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: 2551 <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: "koenig.yvan" <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Deivy Petrescu <email@hidden>)
 >Re: Upgrading to Mavericks - is it likely to break EVERYTHING!? (From: Bryan Harris <email@hidden>)

  • Prev by Date: Export Handlers from Libraries
  • Next by Date: Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?
  • Previous by thread: Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?
  • Next by thread: Re: Upgrading to Mavericks - is it likely to break EVERYTHING!?
  • Index(es):
    • Date
    • Thread