scollege
asked on
Flash function "getTimezoneOffset()" returns wrong offset during DST
Apparently the flash function "getTimezoneOffset()" is buggy - in the sense that it doesn not return the correct Offset during DST. e.g., Offset for EST US during DST should be -4, not -5.
Unfortunately, I cannot find any articles that might suggest how to get around this issue.
Apparently Adobe/Macromedia won't admit to the bug either, as they won't answer my help requests.
Unfortunately, I cannot find any articles that might suggest how to get around this issue.
Apparently Adobe/Macromedia won't admit to the bug either, as they won't answer my help requests.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Um, wait... Interesting...
var _d = new Date();
trace(_d + " : " + _d.getTimezoneOffset());
That script returns this which is -4 hours not -5 hours for EST...
Mon Mar 26 16:56:27 GMT-0400 2007 : 240
CyanBlue
var _d = new Date();
trace(_d + " : " + _d.getTimezoneOffset());
That script returns this which is -4 hours not -5 hours for EST...
Mon Mar 26 16:56:27 GMT-0400 2007 : 240
CyanBlue
ASKER
What version are you using?
I am using FLash MX 2004 - here's what I get (EST US):
Mon Mar 26 17:06:30 GMT-0500 2007 : 300
Of course, the latest DST patches from Microsoft are not working well either, so maybe that has something to do with it.
I am using FLash MX 2004 - here's what I get (EST US):
Mon Mar 26 17:06:30 GMT-0500 2007 : 300
Of course, the latest DST patches from Microsoft are not working well either, so maybe that has something to do with it.
I tested it in Flash MX 2004... I am in EST US as well...
Do me a favor and go check out the Help - About Flash Professional menu and tell me the version numbers you see there...
CyanBlue
Do me a favor and go check out the Help - About Flash Professional menu and tell me the version numbers you see there...
CyanBlue
try it with javascript and see if you get the same result
http://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_gettimezoneoffset
Z
http://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_gettimezoneoffset
Z
ASKER
That would be "7.2"
I have to retract my caustic comments about Flash - turns out my DST settings for Windows TImeZone was off. Once I enabled DST and set the correct time, Flash started returning -4 GMT.
Of course, I can't connect to my network now - but that's a Microsoft issue.
I have to retract my caustic comments about Flash - turns out my DST settings for Windows TImeZone was off. Once I enabled DST and set the correct time, Flash started returning -4 GMT.
Of course, I can't connect to my network now - but that's a Microsoft issue.
You mean this???
WXP - Control Panel - Date and Time - Time Zone
Select(or deselect) Automatically adjust clock for daylight saving changes
???
I don't know why that would make you not able to connect to the network though... Maybe you are talking about something else...
CyanBlue
WXP - Control Panel - Date and Time - Time Zone
Select(or deselect) Automatically adjust clock for daylight saving changes
???
I don't know why that would make you not able to connect to the network though... Maybe you are talking about something else...
CyanBlue
ASKER
From what I understand, a WS's time needs to be in sync with the destination WS or server in order to logon. Ever since the windows DST patch's came out, our network has experienced a lot of these issues. Even though the times on the server and the WS are in sync, many users are still blocked. If the user disables their DST checkbox in their local TIme Zone settings, they can suddenly connect.
Running 'Net time' commands to sync my time with the servers doesn't seem to work.
Anyway, not your problem - my question was answered regarding the Flash function. I will just have to lose more time and find out how to fix the MS problems.
Running 'Net time' commands to sync my time with the servers doesn't seem to work.
Anyway, not your problem - my question was answered regarding the Flash function. I will just have to lose more time and find out how to fix the MS problems.
Ouch... Sorry to hear that and hope you find the solution soon...
CyanBlue
CyanBlue
ASKER
Thanks! We will, I'll just lose more valuable time (and money)...
ASKER
At any rate, the function becomes useless to me.
Maybe I should open a new question - "Where can I get the correct current offset value for the user's timezone"?