Sounds good, thanks.
--- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote:
OK no worries. That's what we do here (setting times to 12 on the
way in and
out of the service). There's a SOAP date type (as opposed to
dateTime), but
we try not to use it because Xfire produces
I'm using version 3 of Flex SDK. I did find a fix, not sure if it's
the right one. I found that the some clients had enough time offset
that it would change there date back on day. This was due to the fact
I'm using a date object, but not using the time part. So I had times
set to 0. I simple
OK no worries. That's what we do here (setting times to 12 on the way in and
out of the service). There's a SOAP date type (as opposed to dateTime), but
we try not to use it because Xfire produces them incorrectly, and Flex's
parser isn't robust enough to handle the rubbish data we get from Xfire
I'm not seeing any specific pattern. I tried another XP machine and
it's working just fine. I've update flash to the newest versions and
still the same issue. I've tried my Linux machine as well, works there
too. Is there a bug? I'm not doing any tricky code with the date.
This post seems to sum up the issue. Anyone have a better answer to
the solution? Is there a simple fix?
http://www.axelscript.com/2008/02/20/timezone-issues-with-remote-datetime-data-and-flash/
What version of Flex are you using, what format is the date when it goes
into text, and how are you getting the results back? Have you checked the
text results coming from the server using something like Charles?
I don't have any experience with Blaze, but plenty with Flex's (occasionally
dodgey)
6 matches
Mail list logo
