summaryrefslogtreecommitdiff
path: root/vcl/inc
diff options
context:
space:
mode:
authorJan-Marek Glogowski <glogow@fbihome.de>2017-01-25 11:22:56 +0100
committerJan-Marek Glogowski <glogow@fbihome.de>2017-07-13 12:10:22 +0200
commitd93acb77667ecdb78b53a1be626ca2e000813828 (patch)
tree43724212eaccd33c68dd78cea46ab8a2b9b17dda /vcl/inc
parentd348035a60361a1b9ba9eb7b67013204a24a6633 (diff)
Correctly account starting tasks
When (re-)starting the system timer for new task, we have to take the already passed time into account to correctly set the new timeout time for the system timer. Change-Id: I1c1c61b3e54bd14d9451c53150251534b2a960f0
Diffstat (limited to 'vcl/inc')
-rw-r--r--vcl/inc/svdata.hxx4
1 files changed, 2 insertions, 2 deletions
diff --git a/vcl/inc/svdata.hxx b/vcl/inc/svdata.hxx
index f9de696650ad..dcbbc00ea9bc 100644
--- a/vcl/inc/svdata.hxx
+++ b/vcl/inc/svdata.hxx
@@ -324,8 +324,8 @@ struct ImplSchedulerContext
ImplSchedulerData* mpFirstSchedulerData = nullptr; ///< list of all active tasks
ImplSchedulerData* mpLastSchedulerData = nullptr; ///< last item of the mpFirstSchedulerData list
SalTimer* mpSalTimer = nullptr; ///< interface to sal event loop / system timer
- sal_uInt64 mnTimerPeriod = 0; ///< current timer period
- sal_uInt64 mnLastProcessTime = 0; ///< last time a task was processed
+ sal_uInt64 mnTimerStart = 0; ///< start time of the timer
+ sal_uInt64 mnTimerPeriod = SAL_MAX_UINT64; ///< current timer period
bool mbNeedsReschedule = false; ///< we need to reschedule
};