-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse support schedule #31
Comments
It's already available as Any suggestions on how to solve this dilemma are appreciated, as is feedback on the module itself. |
Sorry for that. As on the main page, it is written "Mouse support coming soon." I didn't look further. |
No need to apologize, the mouse submodule is supposed to hidden. Otherwise people will start depending on its API and have trouble when it's moved somewhere else, like a separate package. And thank you for your interest in this library. Every piece of feedback makes it better. |
For what it's worth, I think it makes perfect sense to keep mouse & keyboard functionality together in the same library. System APIs usually tap both kinds of devices (at least for Windows). Why not Python modules? Cheers, |
@glitchassassin I understand and agree. But I'm not going down this path for the simplistic reason that I got lucky with the package name "keyboard" and I can't think of any way to describe the combo mouse+keyboard, while:
As you can see this is quite petty, so any and all suggestions are appreciated. |
mouse+keyboard = mouboard or meyboard |
Don't tempt me. I'm going to register them on PyPI as aliases for this package, with credits to you, then we can both share the embarrassment. |
Ha Ha ! Not even afraid ! 😛 |
Any release date for mouse event generation support ?
The text was updated successfully, but these errors were encountered: