QTimeSpan: interest?
-
Great work. I voted for it because I needed this a while ago, and for sure I will need it in the future.
-
Thanks a lot Andre, voted in JIRA.
-
Thanks, André. I voted.
-
A timespan has some pitfalls:
If it uses walltime as the two reference points, you must handle cases where start time is actually after end time. This is because there system time can be updated from a time source (and might jump back in time). IIRC on cell phones this happens quite often, but it can also happen if your desktop system is connected to a NTP time source. It can also happen if you are not connected to a external time source, for instance due to DST changes.
This is also mentioned in the documentation for QTime::elapsed(), which is often used for the same purpose. (actually it says that the result is undefined) -
Thank you for your comment, but that case is handled. The proposed QTimeSpan handles negative time spans just fine.
-
Voted and Watched.
So, after two years, are timespans still not added to Qt? What a shame! -
Note that that is also a due to Sean and me not pushing hard enough to get it in after the first attempt.
-
Useful class - voted.
-
voted too
-
It's very needed class!
+1 -
I need this class, seems to be very useful!!!
-
Hello Andre,
I think QTimeSpan class is really a missing part of the Qt Project. Thanks for yours and Sean's efforts!
I have a question regarding the legality. Is it possible to use your sources in a commercial project (we use Qt with LGPL) as a part of a code-base (do not incorporate it to the Qt libs) before it becomes a part of Qt officially?
Thanks!UPD: English has been slightly improved.
-
I was planning to try and pick this project up again, against Qt 5 and aim for inclusion in 5.2 (finally). I have no objection to others using the code in the meantime, as long as that is in accordance with their usage of Qt.
-
Hi Andre,
What's the current state of QTimeSpan. I could not find any related in Gerrit.
Thanks.
-
There has been no recent active development on it, unfortunately. Life got in the way... Note that the code that is there works just fine.
-
Please update Qt bug report link to https://bugreports.qt.io/browse/QTBUG-16556