@@ -99,13 +99,16 @@ be compiler-neutral: prefer a stable C ABI, named pipe, device interface IOCTL,
9999or similar control channel over passing C++ STL types across that boundary.
100100
101101The current Windows backend selects a UMDF control-channel implementation for
102- ` BackendKind::platform_default ` . It probes ` \\.\LibVirtualHid ` , reports
103- ` requires_installed_driver = true ` , and only advertises gamepad/output-report
104- support when the driver package is installed and the control device can be
105- opened. The client library stays buildable with MSVC and MinGW/UCRT64 because
106- the backend talks to the driver through fixed-size C protocol structures and
107- Win32 ` DeviceIoControl ` calls. The default control device path can be overridden
108- for diagnostics with ` LIBVIRTUALHID_WINDOWS_CONTROL_DEVICE ` .
102+ ` BackendKind::platform_default ` . It always exposes keyboard and mouse through
103+ Win32 ` SendInput ` , then probes ` \\.\LibVirtualHid ` for descriptor-driven virtual
104+ gamepads. It reports ` requires_installed_driver = true ` , and only advertises
105+ gamepad/output-report support when the driver package is installed and the
106+ control device can be opened. Touchscreen, trackpad, and pen tablet support are
107+ not implemented in the Windows backend yet. The client library stays buildable
108+ with MSVC and MinGW/UCRT64 because the gamepad path talks to the driver through
109+ fixed-size C protocol structures and Win32 ` DeviceIoControl ` calls. The default
110+ control device path can be overridden for diagnostics with
111+ ` LIBVIRTUALHID_WINDOWS_CONTROL_DEVICE ` .
109112
110113The UMDF driver uses Windows Virtual HID Framework (VHF) for OS-visible gamepad
111114devices. Create requests start a VHF child device from the requested descriptor,
0 commit comments