HID Clients
The HID Clients are drivers, services or applications that communicate using the HID API and often represent a specific type of device (for example: a sensor, a keyboard, or a mouse). They identify the device via a hardware ID or a specific HID Collection and communicate with the HID Collection via HID API.
In this section
| Topic | Description |
|---|---|
HID usages identify the intended use of HID controls and what the controls actually measure. |
|
A HID collection is a meaningful grouping of HID controls and their respective HID usages. |
|
This section describes how a HID Client can communicate with the HID Class driver (HIDClass) to operate the device’s HID collections. |
|
This section describes the mechanisms that user-mode applications and kernel-mode drivers use for handling HID reports. |
|
User-mode applications and kernel-mode drivers that are HID clients should always free any resources that are no longer required. |
|
This section describes the following requirements for installing HIDClass devices in Microsoft Windows. |
|
This section specifies the hardware IDs that the HID class driver generates for top-level collections. |
|
This topic discusses keyboard and mouse HID client drivers. Keyboards and mice represent the first set of HID clients that were standardized in the HID Usage tables and implemented in Windows operating systems. |
|
Starting with Windows 8, the Windows operating system includes an in-box sensor HID Class driver (SensorsHIDClassDriver.dll), that supports eleven types of sensors that communicate using the HID transport. |
|
Starting with Windows 8, the Windows operating system provides support via HID, for airplane mode radio management controls. |
|
Starting with Windows 8, a standardized solution has been added to allow keyboards (external or embedded on laptops), to control a laptop’s or tablet’s screen brightness through HID. |