Moved a comment to where it belongs.

There was another function between the comment and the one it documented.

Change-Id: I4e96979261738b1ef264984da0d6a8245f2fb643
Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@theqtcompany.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
This commit is contained in:
Edward Welbourne 2015-09-24 12:37:57 +02:00
parent 3130f0865a
commit 1d6643895d

View File

@ -304,15 +304,6 @@ void QFutureWatcherBase::waitForFinished()
futureInterface().waitForFinished();
}
/*! \fn void QFutureWatcher::setPendingResultsLimit(int limit)
The setPendingResultsLimit() provides throttling control. When the number
of pending resultReadyAt() or resultsReadyAt() signals exceeds the
\a limit, the computation represented by the future will be throttled
automatically. The computation will resume once the number of pending
signals drops below the \a limit.
*/
bool QFutureWatcherBase::event(QEvent *event)
{
Q_D(QFutureWatcherBase);
@ -342,6 +333,14 @@ bool QFutureWatcherBase::event(QEvent *event)
return QObject::event(event);
}
/*! \fn void QFutureWatcher::setPendingResultsLimit(int limit)
The setPendingResultsLimit() provides throttling control. When the number
of pending resultReadyAt() or resultsReadyAt() signals exceeds the
\a limit, the computation represented by the future will be throttled
automatically. The computation will resume once the number of pending
signals drops below the \a limit.
*/
void QFutureWatcherBase::setPendingResultsLimit(int limit)
{
Q_D(QFutureWatcherBase);