Report device id on Windows
See original GitHub issueLinux already has this.
Device information is not included in the hook we are using, which complicates things. Raw Input seems to provide this, but it doesn’t include the virtual key codes we use to map most of the key names and keypad status.
There should be some kind of device information on event.device
.
Note: https://github.com/me2d13/luamacros seems to do this.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Device ID string - Windows drivers | Microsoft Learn
A device ID is a string reported by a device's enumerator. A device has only one device ID. A device ID has the...
Read more >Determine the Device Unique ID - WatchGuard Technologies
Open Windows Device Manager. Select the device you want to obtain the ID for. Right-click the device name and select Properties. Select the...
Read more >Using the Windows Device ID utility - TechDocs - Broadcom Inc.
Use the Device ID utility to extract Device Instance ID strings and to determine what devices the system can recognize for detection. You...
Read more >Workspace ONE UEM Data Definitions - VMware Docs
Lists the unique device identifier reported by Google. Apple, macOS (AppleOsX), and Windows. Google Device Report Enabled, Reports if a device has enabled ......
Read more >How to Check the Hardware ID in Device Manager [Quick Guide]
How to find hardware ID Windows 10 using Device Manager · 1. Press the hotkey Win + R to open the Run console....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
any progress on this?
Couple things to consider for interception: The device driver itself is not open source. I tested it locally and found that it doesn’t play very nicely with virtual machines. Namely keyboards will stop working if you disconnect then reconnect (no keystrokes received by the OS). Some other people also found issues with keyboard switches (KVM): https://github.com/oblitum/Interception/issues/145
I think there’s something wrong with the way it handles device reconnect