Just had a small problem, and thought that someone might have similar problems.
I have oldish wireless logitech keyboard+mouse set, which was identified as 2 pieces of mouse (event1 and event2 have both same identification string)
Before:
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Mouse - Logitech USB Receiver [/dev/input/event1]
Mouse - Logitech USB Receiver [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
ATI X10 - X10 Wireless Technology Inc USB Receiver [/dev/input/event6]
That probably caused problems with the scripts since i had no Gizmod.Keyboards[0].
Or at least I think so, as it started to work when i changed the GizmoDeviceStrings.py to map those devices as keyboards. This might render out the possibility to use mouseEvents, but I dont need those, only reliable output of keyboard commands from ATI X10 (Remote Wonder Plus RF).
After:
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - Logitech USB Receiver [/dev/input/event1]
KEyboard - Logitech USB Receiver [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
ATI X10 - X10 Wireless Technology Inc USB Receiver [/dev/input/event6]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just so you know, if you want you can set the device strings to (for example) "event1" or "/dev/input/event2" -- so you can force a device node to be of type "keyboard" or "mouse". That way you can still use the mouse events that get generated from the remote's cursor pad.
I'm hoping to add some more intelligence to the device type detection scheme. In the future there will likely be an "auto" value type, which will tell gizmod to guess at the device type based on some more low level HID descriptor info, and perhaps even based on some simple heuristics that'll look at the type of events being generated from the device.
Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just had a small problem, and thought that someone might have similar problems.
I have oldish wireless logitech keyboard+mouse set, which was identified as 2 pieces of mouse (event1 and event2 have both same identification string)
Before:
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Mouse - Logitech USB Receiver [/dev/input/event1]
Mouse - Logitech USB Receiver [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
ATI X10 - X10 Wireless Technology Inc USB Receiver [/dev/input/event6]
That probably caused problems with the scripts since i had no Gizmod.Keyboards[0].
Or at least I think so, as it started to work when i changed the GizmoDeviceStrings.py to map those devices as keyboards. This might render out the possibility to use mouseEvents, but I dont need those, only reliable output of keyboard commands from ATI X10 (Remote Wonder Plus RF).
After:
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - Logitech USB Receiver [/dev/input/event1]
KEyboard - Logitech USB Receiver [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
ATI X10 - X10 Wireless Technology Inc USB Receiver [/dev/input/event6]
Thanks for the post!
Just so you know, if you want you can set the device strings to (for example) "event1" or "/dev/input/event2" -- so you can force a device node to be of type "keyboard" or "mouse". That way you can still use the mouse events that get generated from the remote's cursor pad.
I'm hoping to add some more intelligence to the device type detection scheme. In the future there will likely be an "auto" value type, which will tell gizmod to guess at the device type based on some more low level HID descriptor info, and perhaps even based on some simple heuristics that'll look at the type of events being generated from the device.
Tim.