The Cuecat probably sends extended scancodes, unfortunately they are not exactly well supported under X, but try xev(1) and observe how the X server responds. You can also switch to the console and try showkey(1) -s and setkeycodes(8). However these programs operate on the console device and when the X server already uses /dev/console for keyboard input you can not access that device.
If xev does not help, since the X server AFAIK does not allow you to add new scancode to keycode mappings, you'll probably either have to use a different (ie USB) keyboard for the X server or you'll have to find a way to get hold of the scancodes in X. I guess game developers might have similiar problems. good luck, Lo > Hi, everyone... > > Anybody remember those Cuecat thingies they were giving away at Radio > Shack a couple years ago? (If you don't, it's basically a hand-held > barcode scanner that plugs into a PS/2 keyboard port via a Y-cable.) > Well, I have one sitting here and I am hoping to be able to use it for a > large inventory project -- 1000+ books, magazines, and comics, all of > which have a handy barcode. > > Currently, when I swipe a barcode with it, nothing at all happens. I'd > expect some kind of code to spew out as if I had typed it in, since this > thing *is* plugged into the keyboard port. > > One possible hitch is that I use software remapping to change a cheap > normal keyboard into a lovely Dvorak layout. (Meaning my /etc/rc.conf > has a line that says KEYMAP="dvorak", and I also use the Dvorak map in > KDE.) However, since I get absolutely *nothing* when I try to scan a > barcode now, I'm guessing the Cuecat's output is somehow separated from > normal keyboard characters... which leads to the guess that it could > somehow be made to work. > > If someone has a clue I could borrow, I'd be very happy. :) -- [EMAIL PROTECTED] mailing list
