... |
... |
@@ -287,28 +287,28 @@ details on the hwdb and how to modify it locally. |
287
|
287
|
.. _faq_timer_offset:
|
288
|
288
|
|
289
|
289
|
------------------------------------------------------------------------------
|
290
|
|
-What causes the "timer offset negative" warning?
|
|
290
|
+What causes the "your system is too slow" warning?
|
291
|
291
|
------------------------------------------------------------------------------
|
292
|
292
|
|
293
|
293
|
libinput relies on the caller to call **libinput_dispatch()** whenever data is
|
294
|
|
-available on the epoll-fd. Doing so will process the state of all devices
|
295
|
|
-and can trigger some timers to be set (e.g. palm detection, tap-to-click,
|
296
|
|
-disable-while-typing, etc.). Internally, libinput's time offsets are always
|
297
|
|
-based on the event time of the triggering event.
|
|
294
|
+available. **libinput_dispatch()** will process the state of all devices,
|
|
295
|
+including some time-sensitive features (e.g. palm detection, tap-to-click,
|
|
296
|
+disable-while-typing, etc.).
|
298
|
297
|
|
299
|
|
-For example, a touch event with time T may trigger a timer for the time T +
|
300
|
|
-180ms. When setting a timer, libinput checks the wall clock time to ensure
|
301
|
|
-that this time T + offset is still in the future. If not, the warning is
|
302
|
|
-logged.
|
|
298
|
+If the time between the event and the call to **libinput_dispatch()**
|
|
299
|
+is excessive, those features may not work correctly. For example, a delay in
|
|
300
|
+touch event processing may cause wrong or missing tap-to-click events or
|
|
301
|
+a palm may not be detected correctly.
|
303
|
302
|
|
304
|
303
|
When this warning appears, it simply means that too much time has passed
|
305
|
|
-between the event occurring (and the epoll-fd triggering) and the current
|
306
|
|
-time. In almost all cases this is an indication of the caller being
|
307
|
|
-overloaded and not handling events as speedily as required.
|
|
304
|
+between the event occurring and the current time. In almost all cases this
|
|
305
|
+is an indication of the caller being overloaded and not handling events as
|
|
306
|
+speedily as required.
|
308
|
307
|
|
309
|
308
|
The warning has no immediate effect on libinput's behavior but some of the
|
310
|
|
-functionality that relies on the timer may be impeded (e.g. palms are not
|
311
|
|
-detected as they should be).
|
|
309
|
+functionality that relies on the timer may be impeded. This is not a bug in
|
|
310
|
+libinput. libinput does not control how quickly **libinput_dispatch()** is
|
|
311
|
+called.
|
312
|
312
|
|
313
|
313
|
.. _faq_wayland:
|
314
|
314
|
|