Hi I wanted to check out the new keyboard hid, so I ran keyboard-flute.ck: [atte@aarhus hid]$ chuck keyboard-flute.ck [chuck](via HID): unable to open /dev/input/mouse0 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse1 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse2 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse3 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck]: HidIn: couldn't open HID device 3:0... I don't know that was supposed to happen, but I guess something else than this :-) Is it me or chuck that is mixing things up? I'm running 1.2.0.6 under Linux... -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions
Hey there, To get HID going in chuck on Linux, you need to set the appropriate permissions on the device files in /dev/input (su -c 'chmod u+r /dev/ input/*' is usually sufficient), so that chuck can read from them (they are read/writable by root only by default). Additionally, keyboard support in linux is still under development, and not currently supported, unfortunately. Documentation on the appropriate interfaces is painfully limited (or perhaps its my googling skills). This is definitely on the way though. spencer On Jul 21, 2006, at 10:43 AM, Atte André Jensen wrote:
Hi
I wanted to check out the new keyboard hid, so I ran keyboard- flute.ck:
[atte@aarhus hid]$ chuck keyboard-flute.ck [chuck](via HID): unable to open /dev/input/mouse0 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse1 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse2 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck](via HID): unable to open /dev/input/mouse3 for reading... ...(note: check permissions if you wish to use mouse devices) [chuck]: HidIn: couldn't open HID device 3:0...
I don't know that was supposed to happen, but I guess something else than this :-) Is it me or chuck that is mixing things up?
I'm running 1.2.0.6 under Linux...
-- peace, love & harmony Atte
http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Spencer Salazar wrote:
To get HID going in chuck on Linux, you need to set the appropriate permissions on the device files in /dev/input
Why? Any device (my mouse or my keyboard) work in other programs, so they must be available with sufficient permissions. Or is possible for such programs because it go through X, or...?
Additionally, keyboard support in linux is still under development, and not currently supported, unfortunately.
That's more plausible to me. When the code in keyboard-flute.ck tries to open a mouse (that's not even present, only /dev/input/mice is available on my system) chuck must be messing things up.
This is definitely on the way though.
Ok, I'll let it go for now, then, although I already imagined 1.000.000 cool things that could be done with this :-) -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions
On Jul 21, 2006, at 12:02 PM, Atte André Jensen wrote:
Spencer Salazar wrote:
To get HID going in chuck on Linux, you need to set the appropriate permissions on the device files in /dev/input
Why? Any device (my mouse or my keyboard) work in other programs, so they must be available with sufficient permissions. Or is possible for such programs because it go through X, or...?
Precisely. To support fun stuff like independently accessing multiple mice and multiple keyboards, we need to read from the devices directly, rather than go through X like everything else. Also, if chuck used X, it would depend on X being installed, which isnt always the case. spencer
Spencer Salazar wrote:
Precisely. To support fun stuff like independently accessing multiple mice and multiple keyboards, we need to read from the devices directly, rather than go through X like everything else. Also, if chuck used X, it would depend on X being installed, which isnt always the case.
Of course... -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions
participants (2)
-
Atte André Jensen -
Spencer Salazar