-
Notifications
You must be signed in to change notification settings - Fork 608
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 #69
Comments
Ok, this gist is fairly more interesting... ;-) |
I have been banging my head and seems I start to understand how it works. According to http://linux.die.net/man/4/console_codes, linux console is capable to emit mouse reports on the stdin stream, so applications like slap could work, so there's no problems here. Point is, linux console doesn't know about the mouse device or its protocol, so needs something that generate the console terminal ioctls (what? :-/) so the console can emit the reports. But how could this be done? This is the first time I've heard about this... :-( Also, all mouse devices can only be read by root. This is not so bad, since the mouse could be used only on the local consoles, so it makes sense to have a global service... Only point, do it in Node.js as it should be, or take a shortcut and use the real gpm and forget of problems about create a clone? |
Posible solution: since |
Ok,
On the other hand, |
It must get boring talking to yourself. Good thing I'm on summer break now! Status update? |
Untested, but definitely feasable since we have access to the |
Ah okay excellent! I'll get to playing with it in my normal set up and see what I get |
Seems to be fairly easy to read the mouse data and a funny project implement the protocol... :-)
https://github.com/telmich/gpm/blob/master/src/gpm2/mice/ps2.c
http://www.computer-engineering.org/ps2mouse/
Also seems now with USB there will be no more protocols, so this is mostly a one-shoot task. Only point is, should this generate ansi-codes on a terminal, w3c mouse events, or this ones should be generated by a higher library (and by the way, keyboard events, too)?
The text was updated successfully, but these errors were encountered: