[Development] Status of QTimeZone

[Jake Thomas Petroules]

I completely agree with that reasoning. Is it too late to restore the original behavior?

I imagine the 5.0.x will be rather short lived with 5.1 coming out so soon so it seems like such a change wouldn't be all that terrible.
-- 
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petroules at petroules.com

On Apr 15, 2013, at 7:11 AM, Mitch Curtis <mitch.curtis at digia.com> wrote:

> On 03/25/2013 10:43 PM, John Layt wrote:
>> 4) The QDateTime QDataStream was changed in 5.0 to write all times as UTC, but
>> I think this is wrong.  Qt::LocalTime is clearly documented as being the same
>> local time (i.e. ymd hms) regardless of the underlying system time or time
>> zone or any changes in the system zone.  The consistent behaviour when
>> serialising would then be to save and restore as the local time and not its
>> UTC equivalent.  For example if I serialise an alarm time of 7am local time, I
>> don't expect that to unserialise as 9am because I changed the system time
>> zone.  If I want a time relative to UTC then I would use UTC, Offset or Time
>> Zone.
> 
> Thiago, do you agree with John here?
> 
> I think it makes sense, and the blame lies on me if so, but I did add 
> you (John) as a reviewer: https://codereview.qt-project.org/#change,32966
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130415/c8417c17/attachment.html>