whytofly
/
qt6-bb10
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix some QElapsedTimer doc grammar issues 

Change-Id: I9bdb0b93b101119477a560b28396f88ea8103745
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
bb10
Jeremy Katz 2012-08-10 14:10:09 +02:00 committed by Qt by Nokia
parent c58a8fa6a6
commit 1fc8f1e49b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/corelib/tools/qelapsedtimer.cpp
View File

@ -91,7 +91,7 @@ QT_BEGIN_NAMESPACE
platforms that support it (see QElapsedTimer::isMonotonic()). This has
the added benefit that QElapsedTimer is immune to time adjustments, such
as the user correcting the time. Also unlike QTime, QElapsedTimer is
immune to changes in the timezone settings, such as daylight savings
immune to changes in the timezone settings, such as daylight saving
periods.
On the other hand, this means QElapsedTimer values can only be compared
@ -112,7 +112,7 @@ QT_BEGIN_NAMESPACE
\section2 32-bit overflows
Some of the clocks that QElapsedTimer have a limited range and may
Some of the clocks used by QElapsedTimer have a limited range and may
overflow after hitting the upper limit (usually 32-bit). QElapsedTimer
deals with this overflow issue and presents a consistent timing. However,
when extracting the time since reference from QElapsedTimer, two
@ -173,7 +173,7 @@ QT_BEGIN_NAMESPACE
counter, which allows avoiding the overflow.
On Windows systems, the clock overflows after 2^32 milliseconds, which
corresponds to roughly 49.7 days. This means two processes's reckoning of
corresponds to roughly 49.7 days. This means two processes' reckoning of
the time since the reference may be different by multiples of 2^32
milliseconds. When comparing such values, it's recommended that the high
32 bits of the millisecond count be masked off.