Codechange: track _realtime_tick more accurate
_realtime_tick was reset every time the diff was calculated. This means if it would trigger, say, every N.9 milliseconds, it would after two iterations already drift a millisecond. This adds up pretty quick.
This commit is contained in:
committed by
Patric Stout
parent
25f6851ca1
commit
5bfa014505
@@ -63,7 +63,7 @@ private:
|
||||
bool edit_box_focused;
|
||||
|
||||
std::chrono::steady_clock::time_point cur_ticks;
|
||||
std::chrono::steady_clock::time_point last_cur_ticks;
|
||||
std::chrono::steady_clock::time_point last_realtime_tick;
|
||||
std::chrono::steady_clock::time_point next_tick;
|
||||
|
||||
int startup_display;
|
||||
|
||||
Reference in New Issue
Block a user