4 ms·
Hi! I've used your library in various projects and am very grateful for it! I figured it'd be worth a shot to ask you this here, since I just caught you: have
by jorl17 5y ago
Hi! I've used your library in various projects and am very grateful for it!
I figured it'd be worth a shot to ask you this here, since I just caught you: have you considered adding some support for "rehooking"/"restarting" the library, so that callees can restart your library whenever they detect that their environment has changed (e.g. input devices have been (dis)connected, etc)?
I've contributed with some info to this issue https://github.com/boppreh/keyboard/issues/264 https://github.com/boppreh/keyboard/issues/264 as to how we're dealing with this in some of our projects. Funnily enough, I didn't know about `python -m keyboard`, and had I known about it, it would definitely have saved me some time!
Once again, thank you very much for your hard work!
- BoppreH 5y agoThanks! I've been thinking about how to handle environment changes for a while, and it's pretty hard to reliably detect and respond to them in all supported systems. But I really like the idea of a manual "re-init" method as temporary measure. This should be trivial in Windows, and doable in Linux after some refactoring. Thanks for the idea, I'll take a look tomorrow.