mirror of
https://gitlab.freedesktop.org/libevdev/libevdev.git
synced 2025-12-24 19:20:06 +01:00
Documentation typo fixes
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
590291513b
commit
f87647b509
1 changed files with 4 additions and 4 deletions
|
|
@ -75,7 +75,7 @@ extern "C" {
|
|||
* Where does libevdev sit?
|
||||
* ========================
|
||||
*
|
||||
* libevdev is essentially a `read(2)` on steroids for `/dev/input/eventX
|
||||
* libevdev is essentially a `read(2)` on steroids for `/dev/input/eventX`
|
||||
* devices. It sits below the process that handles input events, in between
|
||||
* the kernel and that process. In the simplest case, e.g. an evtest-like tool
|
||||
* the stack would look like this:
|
||||
|
|
@ -340,13 +340,13 @@ extern "C" {
|
|||
* @defgroup bits Querying device capabilities
|
||||
*
|
||||
* Abstraction functions to handle device capabilities, specificially
|
||||
* device propeties such as the name of the device and the bits
|
||||
* device properties such as the name of the device and the bits
|
||||
* representing the events suppported by this device.
|
||||
*
|
||||
* The logical state returned may lag behind the physical state of the device.
|
||||
* libevdev queries the device state on libevdev_set_fd() and then relies on
|
||||
* the caller to parse events through libevdev_next_fd(). If a caller does not
|
||||
* use libevdev_next_fd(), libevdev will not update the internal state of the
|
||||
* the caller to parse events through libevdev_next_event(). If a caller does not
|
||||
* use libevdev_next_event(), libevdev will not update the internal state of the
|
||||
* device and thus returns outdated values.
|
||||
*/
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue