Expand description
Wire-format types for HID++ device control that need no device I/O.
These are the addressing scheme (route), read-back snapshots (DPI,
SmartShift), and command/error vocabularies that cross the agent↔GUI IPC
boundary. The actual HID++ transport lives in the sibling openlogi-hid
crate, which re-exports every type here unchanged so its existing callers
keep using openlogi_hid::X; the GUI (a pure IPC client with no device
I/O of its own) depends on this module directly instead of linking the
HID stack.
Re-exports§
pub use dpi::DpiCapabilities;pub use dpi::DpiInfo;pub use error::HidppFeatureErrorKind;pub use error::HidppOperation;pub use error::WriteError;pub use light::LightCommand;pub use light::commands_for_light_settings;pub use pairing::Click;pub use pairing::PairingError;pub use pairing::PasskeyMethod;pub use pairing::ReceiverSelector;pub use route::BOLT_PIDS;pub use route::DIRECT_DEVICE_INDEX;pub use route::DeviceRoute;pub use route::LIGHTSPEED_PIDS;pub use route::UNIFYING_PIDS;pub use route::is_receiver_pid;pub use route::receiver_display_name;pub use route::speaks_unifying_protocol;pub use smartshift::AUTO_DISENGAGE_PERMANENT;pub use smartshift::SmartShiftMode;pub use smartshift::SmartShiftStatus;
Modules§
- dpi
- DPI read-back snapshot and capability math — pure data, no I/O.
- error
- HID++ read/write error vocabulary — pure data, no I/O.
- light
- Semantic standalone-light commands — pure data, no I/O.
- pairing
- Wire-format types for the Bolt/Unifying pairing flow — pure data, no I/O.
- route
- How to reach a controllable HID++ device — addressing data only, no I/O.
- smartshift
- HID++
SmartShift Enhanced(feature0x2111) — wheel ratchet ↔ free-spin control with sensitivity threshold.