Re: The latest AS date and AS Editor bugs
Re: The latest AS date and AS Editor bugs
- Subject: Re: The latest AS date and AS Editor bugs
- From: JF <email@hidden>
- Date: Wed, 22 May 2013 16:09:06 +0100
I made a Big Mistake going to Mountain Lion. I put up with Lion, but I am going back to Snow Leopard over the weekend, if I don't have any weekend work. There are serious interface issues in particular the mouse not working properly in Excel, Illustrator and InDesign, etc.
Just in case anyone else is interested, the latest Mac Mini Server won't instal Snow Leopard. and will not let you start up from an external drive. It does not let you know this until after you try to start up the external drive. I have had to downgrade my new Mac Mini Server to my hobby Mac because it does not fit my work needs, and using my old MacMini (2009) instead. I only miss the 16Gb RAM, I don't miss the lots of total crashes including kernel panics. I'll see how the MMS behaves as a hobby Mac which does not have as many usage demands. Probably cannot get a refund from Apple for this fairly useless Mac.
Sorry, I'm having a whinge, but all of you know how long it takes to back up, clean instal, etc., double checking this and that... .
Wed, 22 May 2013 15:37:43 +0100, Nigel Garvey wrote:
>Hi all.
>
>Just a heads-up as I haven't seen these mentioned elsewhere.
>
>I upgraded my MacBook Pro from Snow Leopard to Mountain Lion a week or
>two ago and it seems that AppleScript dates still haven't returned to
>the golden age of Tiger, when they apparently had no bugs at all.
>
>The Leopard/Snow Leopard "Julian date string" bugs have been fixed, but
>there's now a 75-second discrepancy between date texts and other date
>properties which affects all dates up to and including 1 December 1847
>00:01:14. eg.:
>
> -- (Rearrange this specifier to compile on your own machine.)
> tell date "Thursday 31 December 1846 23:59:59" to ¬
> return its {weekday, day, month, year, hours, minutes, seconds, date
>string}
> --> {Friday, 1, January, 1847, 0, 1, 14, "Thursday 31 December 1846"}
>
>
>In a separate development, all dates from 1 January 3514 00:00:00 on,
>when compiled or derived from specifiers, are now transposed to the 20th
>or 21st centuries:
>
> tell date "1/1/3514" to ¬
> return its {weekday, day, month, year, hours, minutes, seconds, date
>string}
> --> {Wednesday, 1, January, 2014, 0, 0, 0, "Wednesday 1 January 2014"}
>
>If the last two digits of the specified year are in the range 00-49, the
>first two digits of the returned year are 20, otherwise they're 19.
>However, dates in this last 72% of the AppleScript date range (if it's
>still officially the years 1000 to 9999) can successfully be derived by
>addition or property setting from dates in the range 1 December 1847
>00:01:15 to 31 December 3513 23:59:59.
>
>
>AppleScript Editor's ability to let you accidentally save uncompiled
>changes and send useless scripts to people with earlier systems has been
>mentioned before. It also turns out to be impossible to compile a script
>in a new document which has been created and named by a script. Or
>rather, the text formats as if compiled, but then there are a couple of
>stupid dialogs about duplicates and the file not being found, after
>which the text unformats. :\
>
>NG
>
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>AppleScript-Users mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>@fmail.co.uk
>Archives: http://lists.apple.com/archives/applescript-users
>
>This email sent to email@hidden
_______________________________________________
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