2011-04-27 10:05:43 +00:00
|
|
|
/****************************************************************************
|
|
|
|
**
|
2012-01-05 04:03:39 +00:00
|
|
|
** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
|
2012-01-20 03:06:31 +00:00
|
|
|
** Contact: http://www.qt-project.org/
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
** This file is part of the QtCore module of the Qt Toolkit.
|
|
|
|
**
|
|
|
|
** $QT_BEGIN_LICENSE:LGPL$
|
|
|
|
** GNU Lesser General Public License Usage
|
2011-05-24 09:34:08 +00:00
|
|
|
** This file may be used under the terms of the GNU Lesser General Public
|
|
|
|
** License version 2.1 as published by the Free Software Foundation and
|
|
|
|
** appearing in the file LICENSE.LGPL included in the packaging of this
|
|
|
|
** file. Please review the following information to ensure the GNU Lesser
|
|
|
|
** General Public License version 2.1 requirements will be met:
|
|
|
|
** http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
** In addition, as a special exception, Nokia gives you certain additional
|
2011-05-24 09:34:08 +00:00
|
|
|
** rights. These rights are described in the Nokia Qt LGPL Exception
|
2011-04-27 10:05:43 +00:00
|
|
|
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
|
|
|
|
**
|
2011-05-24 09:34:08 +00:00
|
|
|
** GNU General Public License Usage
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU General
|
|
|
|
** Public License version 3.0 as published by the Free Software Foundation
|
|
|
|
** and appearing in the file LICENSE.GPL included in the packaging of this
|
|
|
|
** file. Please review the following information to ensure the GNU General
|
|
|
|
** Public License version 3.0 requirements will be met:
|
|
|
|
** http://www.gnu.org/copyleft/gpl.html.
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
2011-05-24 09:34:08 +00:00
|
|
|
** Other Usage
|
|
|
|
** Alternatively, this file may be used in accordance with the terms and
|
|
|
|
** conditions contained in a signed written agreement between you and Nokia.
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
2012-01-24 06:17:24 +00:00
|
|
|
**
|
2011-04-27 10:05:43 +00:00
|
|
|
** $QT_END_LICENSE$
|
|
|
|
**
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
#include "qtimer.h"
|
|
|
|
#include "qabstracteventdispatcher.h"
|
|
|
|
#include "qcoreapplication.h"
|
|
|
|
#include "qobject_p.h"
|
|
|
|
|
|
|
|
QT_BEGIN_NAMESPACE
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\class QTimer
|
2012-08-23 10:22:38 +00:00
|
|
|
\inmodule QtCore
|
2011-04-27 10:05:43 +00:00
|
|
|
\brief The QTimer class provides repetitive and single-shot timers.
|
|
|
|
|
|
|
|
\ingroup events
|
|
|
|
|
|
|
|
|
|
|
|
The QTimer class provides a high-level programming interface for
|
|
|
|
timers. To use it, create a QTimer, connect its timeout() signal
|
2012-09-08 17:06:23 +00:00
|
|
|
to the appropriate slots, and call start(). From then on, it will
|
2011-04-27 10:05:43 +00:00
|
|
|
emit the timeout() signal at constant intervals.
|
|
|
|
|
|
|
|
Example for a one second (1000 millisecond) timer (from the
|
|
|
|
\l{widgets/analogclock}{Analog Clock} example):
|
|
|
|
|
2012-08-29 08:25:56 +00:00
|
|
|
\snippet widgets/analogclock/analogclock.cpp 4
|
|
|
|
\snippet widgets/analogclock/analogclock.cpp 5
|
|
|
|
\snippet widgets/analogclock/analogclock.cpp 6
|
2011-04-27 10:05:43 +00:00
|
|
|
|
|
|
|
From then on, the \c update() slot is called every second.
|
|
|
|
|
|
|
|
You can set a timer to time out only once by calling
|
|
|
|
setSingleShot(true). You can also use the static
|
|
|
|
QTimer::singleShot() function to call a slot after a specified
|
|
|
|
interval:
|
|
|
|
|
2012-03-20 18:37:07 +00:00
|
|
|
\snippet timers/timers.cpp 3
|
2011-04-27 10:05:43 +00:00
|
|
|
|
|
|
|
In multithreaded applications, you can use QTimer in any thread
|
|
|
|
that has an event loop. To start an event loop from a non-GUI
|
|
|
|
thread, use QThread::exec(). Qt uses the timer's
|
|
|
|
\l{QObject::thread()}{thread affinity} to determine which thread
|
|
|
|
will emit the \l{QTimer::}{timeout()} signal. Because of this, you
|
|
|
|
must start and stop the timer in its thread; it is not possible to
|
|
|
|
start a timer from another thread.
|
|
|
|
|
|
|
|
As a special case, a QTimer with a timeout of 0 will time out as
|
|
|
|
soon as all the events in the window system's event queue have
|
|
|
|
been processed. This can be used to do heavy work while providing
|
|
|
|
a snappy user interface:
|
|
|
|
|
2012-03-20 18:37:07 +00:00
|
|
|
\snippet timers/timers.cpp 4
|
|
|
|
\snippet timers/timers.cpp 5
|
|
|
|
\snippet timers/timers.cpp 6
|
2011-04-27 10:05:43 +00:00
|
|
|
|
2012-09-08 17:06:23 +00:00
|
|
|
From then on, \c processOneThing() will be called repeatedly. It
|
2011-04-27 10:05:43 +00:00
|
|
|
should be written in such a way that it always returns quickly
|
|
|
|
(typically after processing one data item) so that Qt can deliver
|
2012-09-08 17:06:23 +00:00
|
|
|
events to the user interface and stop the timer as soon as it has done all
|
2011-04-27 10:05:43 +00:00
|
|
|
its work. This is the traditional way of implementing heavy work
|
2012-09-08 17:06:23 +00:00
|
|
|
in GUI applications, but as multithreading is nowadays becoming available on
|
|
|
|
more and more platforms, we expect that zero-millisecond
|
2011-04-27 10:05:43 +00:00
|
|
|
QTimers will gradually be replaced by \l{QThread}s.
|
|
|
|
|
|
|
|
\section1 Accuracy and Timer Resolution
|
|
|
|
|
|
|
|
Timers will never time out earlier than the specified timeout value
|
|
|
|
and they are not guaranteed to time out at the exact value specified.
|
|
|
|
In many situations, they may time out late by a period of time that
|
|
|
|
depends on the accuracy of the system timers.
|
|
|
|
|
|
|
|
The accuracy of timers depends on the underlying operating system
|
|
|
|
and hardware. Most platforms support a resolution of 1 millisecond,
|
|
|
|
though the accuracy of the timer will not equal this resolution
|
|
|
|
in many real-world situations.
|
|
|
|
|
|
|
|
If Qt is unable to deliver the requested number of timer clicks,
|
|
|
|
it will silently discard some.
|
|
|
|
|
|
|
|
\section1 Alternatives to QTimer
|
|
|
|
|
|
|
|
An alternative to using QTimer is to call QObject::startTimer()
|
|
|
|
for your object and reimplement the QObject::timerEvent() event
|
|
|
|
handler in your class (which must inherit QObject). The
|
|
|
|
disadvantage is that timerEvent() does not support such
|
|
|
|
high-level features as single-shot timers or signals.
|
|
|
|
|
2012-09-08 17:06:23 +00:00
|
|
|
Another alternative is QBasicTimer. It is typically less
|
|
|
|
cumbersome than using QObject::startTimer()
|
2011-04-27 10:05:43 +00:00
|
|
|
directly. See \l{Timers} for an overview of all three approaches.
|
|
|
|
|
|
|
|
Some operating systems limit the number of timers that may be
|
|
|
|
used; Qt tries to work around these limitations.
|
|
|
|
|
|
|
|
\sa QBasicTimer, QTimerEvent, QObject::timerEvent(), Timers,
|
|
|
|
{Analog Clock Example}, {Wiggly Example}
|
|
|
|
*/
|
|
|
|
|
|
|
|
static const int INV_TIMER = -1; // invalid timer id
|
|
|
|
|
|
|
|
/*!
|
|
|
|
Constructs a timer with the given \a parent.
|
|
|
|
*/
|
|
|
|
|
|
|
|
QTimer::QTimer(QObject *parent)
|
2011-12-21 10:32:43 +00:00
|
|
|
: QObject(parent), id(INV_TIMER), inter(0), del(0), single(0), nulltimer(0), type(Qt::CoarseTimer)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*!
|
|
|
|
Destroys the timer.
|
|
|
|
*/
|
|
|
|
|
|
|
|
QTimer::~QTimer()
|
|
|
|
{
|
|
|
|
if (id != INV_TIMER) // stop running timer
|
|
|
|
stop();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\fn void QTimer::timeout()
|
|
|
|
|
|
|
|
This signal is emitted when the timer times out.
|
|
|
|
|
|
|
|
\sa interval, start(), stop()
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\property QTimer::active
|
|
|
|
\since 4.3
|
|
|
|
|
|
|
|
This boolean property is true if the timer is running; otherwise
|
|
|
|
false.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\fn bool QTimer::isActive() const
|
|
|
|
|
|
|
|
Returns true if the timer is running (pending); otherwise returns
|
|
|
|
false.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\fn int QTimer::timerId() const
|
|
|
|
|
|
|
|
Returns the ID of the timer if the timer is running; otherwise returns
|
|
|
|
-1.
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
/*! \overload start()
|
|
|
|
|
|
|
|
Starts or restarts the timer with the timeout specified in \l interval.
|
|
|
|
|
2011-05-10 17:52:50 +00:00
|
|
|
If the timer is already running, it will be
|
|
|
|
\l{QTimer::stop()}{stopped} and restarted.
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
If \l singleShot is true, the timer will be activated only once.
|
|
|
|
*/
|
|
|
|
void QTimer::start()
|
|
|
|
{
|
|
|
|
if (id != INV_TIMER) // stop running timer
|
|
|
|
stop();
|
|
|
|
nulltimer = (!inter && single);
|
2011-12-21 10:32:43 +00:00
|
|
|
id = QObject::startTimer(inter, Qt::TimerType(type));
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*!
|
|
|
|
Starts or restarts the timer with a timeout interval of \a msec
|
|
|
|
milliseconds.
|
2011-05-10 17:52:50 +00:00
|
|
|
|
|
|
|
If the timer is already running, it will be
|
|
|
|
\l{QTimer::stop()}{stopped} and restarted.
|
|
|
|
|
|
|
|
If \l singleShot is true, the timer will be activated only once.
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
*/
|
|
|
|
void QTimer::start(int msec)
|
|
|
|
{
|
|
|
|
inter = msec;
|
|
|
|
start();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*!
|
|
|
|
Stops the timer.
|
|
|
|
|
|
|
|
\sa start()
|
|
|
|
*/
|
|
|
|
|
|
|
|
void QTimer::stop()
|
|
|
|
{
|
|
|
|
if (id != INV_TIMER) {
|
|
|
|
QObject::killTimer(id);
|
|
|
|
id = INV_TIMER;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\reimp
|
|
|
|
*/
|
|
|
|
void QTimer::timerEvent(QTimerEvent *e)
|
|
|
|
{
|
|
|
|
if (e->timerId() == id) {
|
|
|
|
if (single)
|
|
|
|
stop();
|
|
|
|
emit timeout();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
class QSingleShotTimer : public QObject
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
int timerId;
|
|
|
|
public:
|
|
|
|
~QSingleShotTimer();
|
2012-09-13 18:23:10 +00:00
|
|
|
QSingleShotTimer(int msec, Qt::TimerType timerType, const QObject *r, const char * m);
|
2011-04-27 10:05:43 +00:00
|
|
|
Q_SIGNALS:
|
|
|
|
void timeout();
|
|
|
|
protected:
|
|
|
|
void timerEvent(QTimerEvent *);
|
|
|
|
};
|
|
|
|
|
2012-09-13 18:23:10 +00:00
|
|
|
QSingleShotTimer::QSingleShotTimer(int msec, Qt::TimerType timerType, const QObject *receiver, const char *member)
|
2011-04-27 10:05:43 +00:00
|
|
|
: QObject(QAbstractEventDispatcher::instance())
|
|
|
|
{
|
|
|
|
connect(this, SIGNAL(timeout()), receiver, member);
|
2011-12-21 10:32:43 +00:00
|
|
|
timerId = startTimer(msec, timerType);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
QSingleShotTimer::~QSingleShotTimer()
|
|
|
|
{
|
|
|
|
if (timerId > 0)
|
|
|
|
killTimer(timerId);
|
|
|
|
}
|
|
|
|
|
|
|
|
void QSingleShotTimer::timerEvent(QTimerEvent *)
|
|
|
|
{
|
|
|
|
// need to kill the timer _before_ we emit timeout() in case the
|
|
|
|
// slot connected to timeout calls processEvents()
|
|
|
|
if (timerId > 0)
|
|
|
|
killTimer(timerId);
|
|
|
|
timerId = -1;
|
|
|
|
emit timeout();
|
|
|
|
|
|
|
|
// we would like to use delete later here, but it feels like a
|
|
|
|
// waste to post a new event to handle this event, so we just unset the flag
|
|
|
|
// and explicitly delete...
|
|
|
|
qDeleteInEventHandler(this);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\reentrant
|
|
|
|
This static function calls a slot after a given time interval.
|
|
|
|
|
|
|
|
It is very convenient to use this function because you do not need
|
2012-05-11 00:38:45 +00:00
|
|
|
to bother with a \l{QObject::timerEvent()}{timerEvent} or
|
2011-04-27 10:05:43 +00:00
|
|
|
create a local QTimer object.
|
|
|
|
|
|
|
|
Example:
|
2012-03-20 18:37:07 +00:00
|
|
|
\snippet code/src_corelib_kernel_qtimer.cpp 0
|
2011-04-27 10:05:43 +00:00
|
|
|
|
|
|
|
This sample program automatically terminates after 10 minutes
|
|
|
|
(600,000 milliseconds).
|
|
|
|
|
|
|
|
The \a receiver is the receiving object and the \a member is the
|
|
|
|
slot. The time interval is \a msec milliseconds.
|
|
|
|
|
|
|
|
\sa start()
|
|
|
|
*/
|
|
|
|
|
2012-09-13 18:23:10 +00:00
|
|
|
void QTimer::singleShot(int msec, const QObject *receiver, const char *member)
|
2011-12-21 10:32:43 +00:00
|
|
|
{
|
2011-12-21 10:33:07 +00:00
|
|
|
// coarse timers are worst in their first firing
|
|
|
|
// so we prefer a high precision timer for something that happens only once
|
|
|
|
// unless the timeout is too big, in which case we go for coarse anyway
|
|
|
|
singleShot(msec, msec >= 2000 ? Qt::CoarseTimer : Qt::PreciseTimer, receiver, member);
|
2011-12-21 10:32:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*! \overload
|
|
|
|
\reentrant
|
|
|
|
This static function calls a slot after a given time interval.
|
|
|
|
|
|
|
|
It is very convenient to use this function because you do not need
|
2012-05-11 00:38:45 +00:00
|
|
|
to bother with a \l{QObject::timerEvent()}{timerEvent} or
|
2011-12-21 10:32:43 +00:00
|
|
|
create a local QTimer object.
|
|
|
|
|
|
|
|
The \a receiver is the receiving object and the \a member is the slot. The
|
|
|
|
time interval is \a msec milliseconds. The \a timerType affects the
|
|
|
|
accuracy of the timer.
|
|
|
|
|
|
|
|
\sa start()
|
|
|
|
*/
|
2012-09-13 18:23:10 +00:00
|
|
|
void QTimer::singleShot(int msec, Qt::TimerType timerType, const QObject *receiver, const char *member)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
|
|
|
if (receiver && member) {
|
|
|
|
if (msec == 0) {
|
|
|
|
// special code shortpath for 0-timers
|
|
|
|
const char* bracketPosition = strchr(member, '(');
|
2012-04-22 21:11:07 +00:00
|
|
|
if (!bracketPosition || !(member[0] >= '0' && member[0] <= '2')) {
|
2011-04-27 10:05:43 +00:00
|
|
|
qWarning("QTimer::singleShot: Invalid slot specification");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
QByteArray methodName(member+1, bracketPosition - 1 - member); // extract method name
|
2012-09-13 18:23:10 +00:00
|
|
|
QMetaObject::invokeMethod(const_cast<QObject *>(receiver), methodName.constData(), Qt::QueuedConnection);
|
2011-04-27 10:05:43 +00:00
|
|
|
return;
|
|
|
|
}
|
2011-12-21 10:32:43 +00:00
|
|
|
(void) new QSingleShotTimer(msec, timerType, receiver, member);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\property QTimer::singleShot
|
|
|
|
\brief whether the timer is a single-shot timer
|
|
|
|
|
|
|
|
A single-shot timer fires only once, non-single-shot timers fire
|
|
|
|
every \l interval milliseconds.
|
|
|
|
|
|
|
|
\sa interval, singleShot()
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\property QTimer::interval
|
|
|
|
\brief the timeout interval in milliseconds
|
|
|
|
|
|
|
|
The default value for this property is 0. A QTimer with a timeout
|
|
|
|
interval of 0 will time out as soon as all the events in the window
|
|
|
|
system's event queue have been processed.
|
|
|
|
|
|
|
|
Setting the interval of an active timer changes its timerId().
|
|
|
|
|
|
|
|
\sa singleShot
|
|
|
|
*/
|
|
|
|
void QTimer::setInterval(int msec)
|
|
|
|
{
|
|
|
|
inter = msec;
|
|
|
|
if (id != INV_TIMER) { // create new timer
|
|
|
|
QObject::killTimer(id); // restart timer
|
2011-12-21 10:32:43 +00:00
|
|
|
id = QObject::startTimer(msec, Qt::TimerType(type));
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Add a remainingTime() method to the public interface of the QTimer class
It is an extension coming from the use case when you, for instance, need to
implement a countdown timer in client codes, and manually maintain a dedicated
variable for counting down with the help of yet another Timer. There might be
other use cases as well. The returned value is meant to be in milliseconds, as
the method documentation says, since it is reasonable, and consistent with the
rest (ie. the interval accessor).
The elapsed time is already being tracked inside the event dispatcher, thus the
effort is only exposing that for all platforms supported according to the
desired timer identifier, and propagating up to the QTimer public API. It is
done by using the QTimerInfoList class in the glib and unix dispatchers, and the
WinTimeInfo struct for the windows dispatcher.
It might be a good idea to to establish a QWinTimerInfo
(qtimerinfo_win{_p.h,cpp}) in the future for resembling the interface for
windows with the glib/unix management so that it would be consistent. That would
mean abstracting out a base class (~interface) for the timer info classes.
Something like that QAbstractTimerInfo.
Test: Build test only on (Arch)Linux, Windows and Mac. I have also run the unit
tests and they passed as well.
Change-Id: Ie37b3aff909313ebc92e511e27d029abb070f110
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
2012-02-23 05:41:30 +00:00
|
|
|
/*!
|
|
|
|
\property QTimer::remainingTime
|
|
|
|
\brief the remaining time in milliseconds
|
|
|
|
|
|
|
|
Returns the timer's remaining value in milliseconds left until the timeout.
|
|
|
|
If the timer is inactive, the returned value will be -1. If the timer is
|
|
|
|
overdue, the returned value will be 0.
|
|
|
|
|
|
|
|
\sa interval
|
|
|
|
*/
|
|
|
|
int QTimer::remainingTime() const
|
|
|
|
{
|
|
|
|
if (id != INV_TIMER) {
|
|
|
|
return QAbstractEventDispatcher::instance()->remainingTime(id);
|
|
|
|
}
|
|
|
|
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2011-12-21 10:32:43 +00:00
|
|
|
/*!
|
|
|
|
\property QTimer::timerType
|
|
|
|
\brief controls the accuracy of the timer
|
|
|
|
|
|
|
|
The default value for this property is \c Qt::CoarseTimer.
|
|
|
|
|
|
|
|
\sa Qt::TimerType
|
|
|
|
*/
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QT_END_NAMESPACE
|
2012-09-03 14:56:48 +00:00
|
|
|
|
|
|
|
#include "qtimer.moc"
|