MACSCRPT Archives

July 2014

MACSCRPT@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type:
text/plain; charset=windows-1252
Date:
Fri, 11 Jul 2014 10:06:23 -0700
Reply-To:
Macintosh Scripting Systems <[log in to unmask]>
Subject:
From:
kee nethery <[log in to unmask]>
Message-ID:
In-Reply-To:
Content-Transfer-Encoding:
quoted-printable
Sender:
Macintosh Scripting Systems <[log in to unmask]>
Parts/Attachments:
text/plain (24 lines)
Will do, thanks! Sounds like we absolutely need tests that watch for when xcode applescript stops working so that we can file bugs asap.
Kee


On Jul 10, 2014, at 10:22 PM, Jon Pugh <[log in to unmask]> wrote:

> On Jul 10, 2014, at 8:11 PM, Shane Stanley wrote:
>> On 11 Jul 2014, at 3:00 am, kee nethery <[log in to unmask]> wrote:
>> 
>>> If you write AppleScripts on a regular basis, you know that some dictionary entries might not work as advertised
>> 
>> In the case of Xcode, that's a bit of an understatement. The dictionary is pretty much what worked in Xcode 3, and whether any particular part works now is entirely pot luck.
>> 
>> That's not to say some of your scripts can't be written, but you'd need to keep your fingers crossed with every upgrade. I gave up.
>> 
>> Mind you, extra requests to bugreport.apple.com can't hurt.
> 
> I heard a while back that Sal was trying to find a way to get scripting support back into Xcode but I don’t think he had much luck.  The team didn’t have time and it wasn’t viewed as sufficiently important.
> 
> So send in those bug reports.
> 
> Jon
> 

ATOM RSS1 RSS2