OK, it looks like it definitely is a daylight-saving problem. My system worked fine until I told it I was in Sydney instead of Brisbane. Then I get the one hour discrepancy. BUT, if you set useSystemDate, you get the correct hour - then the date goes a bit funny:

With my clock set to Brisbane (+10, no daylight-saving):
set the useSystemDate to true
ask "Enter a time:" with "8:17 am"
convert it to seconds
convert it to internet date

I get:
        Sun, 11 Jan 1970 08:17:00 +1000

Removing the first line (useSystemDate), I get:
Thu, 6 Nov 2003 08:17:00 +1000
i.e. it fills in the empty date with today's date, rather than a zero date.


Now setting my clock to Sydney time (+10 but with daylight-saving), I get:
With useSystemDate set to true:
Sun, 11 Jan 1970 08:17:00 +1000
With useSystemDate not set:
Thu, 6 Nov 2003 09:17:00 +1000


So, always set useSystemDate to true and don't expect it to fill in a blank date with today's. Hopefully this should be enough to get Jonathan out of trouble :-)

Cheers,
Sarah

On Thursday, November 6, 2003, at 12:16 pm, Monte Goulding wrote:


I get the correct answers using OS X 10.2.8 and set to Australian time
BUT I am in Queensland so I'm not on daylight saving. I wonder is that
a factor. Could you try converting to "the internet date"? Using your
8:17 am example, I get: Thu, 6 Nov 2003 08:17:00 +1000

Hmmm... I'm in Adelaide and i get the problem so perhaps it is daylight saving???

Monte

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution




_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to