before 7.0.3, if we had a
HighResolutionTimer running with a long period (t1), and we would call
startTimer() on it with a shorter interval (t2), the next callback was happening after that short time t2.
with 7.0.3, the new behavior is that the next callback will happen after the current (long) period is finished. Only after that the new interval will be taken into account.
Could you add a
startTimer() so that we get the previous behaviour back?