diff options
| author | Robin Burchell <robin.burchell@crimson.no> | 2017-02-28 03:55:18 +1100 |
|---|---|---|
| committer | Robin Burchell <robin.burchell@crimson.no> | 2017-04-11 14:26:16 +0000 |
| commit | b018a5ecef7b12c2d28df950a207ff3c7fc3abed (patch) | |
| tree | 9af29544ea8a35fa6a2331d0d2735ba2c05dc929 /src/widgets/widgets/qdialogbuttonbox.cpp | |
| parent | e91726ef9e09a084aad21d3ee27f6e2299908947 (diff) | |
QAndroidPlatformScreen: Use an event rather than a QTimer
It looks like the origins of this timer may come from QFbScreen. QFbScreen,
however, changed away from a timer in d7068cbe1b37eb065c1902c8e944f3bc19db0ba4.
There are other reasons to avoid a timer in this case, though: a timer may be
pre-empted by application events (like other timers), which may mean a
significant amount of time could pass between starting the timer and pushing the
contents out to the actual screen (in doRedraw).
This has the effect that flush becomes synchronous, which matches the
behavior of the other platforms as far as I can tell.
Change-Id: Ic67ae6c82945a247dceac44ee1bf7d2940f79d07
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Diffstat (limited to 'src/widgets/widgets/qdialogbuttonbox.cpp')
0 files changed, 0 insertions, 0 deletions