SmartGWT version: latest from showcase
Browser: latest Chrome and Firefox 26 (development) tested
If you set a specific timezone via DateUtil API different from machine's timezone the range of hours in Calendar start from 00:00 -/+ time zone specified instead of 00:00 (or 12:00 pm). Is this the normal behaviour? This can be tested against today's build in the showcase changing in the console the timezone and switching to another day. See attached image. Setting UTC-5 when being UTC+1, as you can see, calendar starts in 6pm
We found this because we have two similar versions of a project wich one needs to run in spanish timezone and the other one in mexican timezone. Both of them running in the same machines, and we don't want administration workers to change machine's local time every time they change the web app. If this is the normal behaviour, what can we do as workaroung?
Best regards
Browser: latest Chrome and Firefox 26 (development) tested
If you set a specific timezone via DateUtil API different from machine's timezone the range of hours in Calendar start from 00:00 -/+ time zone specified instead of 00:00 (or 12:00 pm). Is this the normal behaviour? This can be tested against today's build in the showcase changing in the console the timezone and switching to another day. See attached image. Setting UTC-5 when being UTC+1, as you can see, calendar starts in 6pm
We found this because we have two similar versions of a project wich one needs to run in spanish timezone and the other one in mexican timezone. Both of them running in the same machines, and we don't want administration workers to change machine's local time every time they change the web app. If this is the normal behaviour, what can we do as workaroung?
Best regards
Comment