WinKeyMacros is supposed to allow you to use multiple keyboards as individual ones on Windows. You can set the keys of a second/third/[...] keyboard as macro keys (eg. key 'k' on second keyboard, would execute sequence 'hello world').
WinKeyMacros is composed from the following:
- KeyboardFilterDriverKMDF -> A windows kernel driver, which can intercept and inject keys at kernel-level depending on the source(keyboard) of the key input
- MacroLibrary -> A library that enables easy communication with the driver (an APP can talk directly to the driver without this, but will have to implement IOCTLs communication by itself, the library takes care of that and offers an easier api)
- The app -> This is not yet ready, there is an example console app (ConsoleCommunicationTest), but the objective is to have a GUI APP which should be easy to use for anyone, even not techy persons.
Currently, the driver is almost finished and can be found inside KeyboardFilterDriverKMDF directory. For easier communication with the driver, there is a library that can be used to communicate with it, found inside MacroLibrary directory. An example app implementing MacroLibrary can be found in ConsoleCommunicationTest directory.
For more information of how the driver works, check the README.md from the driver directory and comments from it's code.
Current project goals:
- Build an UI app to manage macros
- Find a signer for the driver (Microsoft requires signing drivers for Win10 with an EV certificate, which can only bought by a business and costs a lot of money and which, unfortunately, could kill this project)
Current project barrier:
- Microsoft requires all drivers to be signed using an "EV Certificate". EV Certificates can only be obtained by companies and they cost quite some money (some of them go for more than 500$/year) and because of this, hobby driver development is discouraged by Microsoft. Unfortunately, I'll have to stop development for this package (driver and the app) as there is no way for me to put my hands on an EV certificate and be able to release the package for public use. This may change however, when and if Microsoft decides to allow hobby driver developers to get their hands on a certificate and publish drivers.
The package is launched under LGPLv2.1 License, which means you are free to distribute the driver with your own application without disclosing the source code of your application as long as you do not make any modification on the driver's source code itself. If custom licensing is required, feel free to contact me and we can discuss it.