Re: programable buttons
I just got one of those keyboards. showkeys shows me no keycodes but in the syslog I found following: Mar 12 21:34:11 matthschulzg kernel: keyboard: unknown scancode e0 2e Mar 12 21:34:11 matthschulzg kernel: keyboard: unknown scancode e0 2e Mar 12 21:34:17 matthschulzg kernel: keyboard: unknown scancode e0 12 Mar 12 21:34:17 matthschulzg kernel: keyboard: unknown scancode e0 12 Mar 12 21:35:54 matthschulzg kernel: keyboard: unknown scancode e0 22 Mar 12 21:35:55 matthschulzg kernel: keyboard: unknown scancode e0 22 Mar 12 21:35:55 matthschulzg kernel: keyboard: unknown scancode e0 24 Mar 12 21:35:55 matthschulzg kernel: keyboard: unknown scancode e0 24 ... Any ideas? Matth On Sat, 11 Mar 2000, Blu wrote: > Trevor Reed wrote: > > > > I have a Compaq Armada 4130T with debian installed. I have X working > > perfectly, but I haven't tried sound yet. I have also not been able to find > > out anything about the programmable buttons. Other than that, i is really > > great!! > > > > Hello, > > About the programmable buttons, they are just like regular keys. There > is a little program which shows you the codes returned when you press a > key (I don't remember the name). You could use it to get the keycodes of > the buttons and then bind them to whatever action you want. > > Blu.
Re: programable buttons
> --- Blu <[EMAIL PROTECTED]> wrote: > > Trevor Reed wrote: > > > I have a Compaq Armada 4130T ... X working ... > > > also not been able to find out anything about the programmable buttons. > > > > Hello, > > About the programmable buttons, they are just like regular keys. There > > is a little program which shows you the codes ... > > Blu. > > The program is "showkeys". As for making it a macro, > the only really free-form way I found was binding a > key to Keyboard_Signal and then defining the action in > inittab. Unfortunately, this limits to one > user-defined key. Has anyone else figured out a better > way to do this stuff? Look for howto's about swapping capslock and control, then expand the descriptions to meet your own uses. Once you know a key's codes it should be possible to assign it features in xmodmap. (In fact that used to be about all you could do with it; most people didn't know about keyboard_signal.) Quite common to set them to fill up the rest of the bank of allowed shifting flavors, then create macros on combinations with those. For example abandon Alt-foo to the app author's delusions of "intuitive user interface" and put anything of your own on the custom ones, abusing one of the meta's usually set aside for toggling to kanji or some other wacky character set (assuming, that your laptop has no need for a wacky character set :-) It could be interesting to feel like you've moved the numlock key by remapping it into one of these, should you like their placement better. * Heather
Re: programable buttons
--- Blu <[EMAIL PROTECTED]> wrote: > Trevor Reed wrote: > > > > I have a Compaq Armada 4130T with debian > installed. I have X working > > perfectly, but I haven't tried sound yet. I have > also not been able to find > > out anything about the programmable buttons. > Other than that, i is really > > great!! > > > > Hello, > > About the programmable buttons, they are just like > regular keys. There > is a little program which shows you the codes > returned when you press a > key (I don't remember the name). You could use it to > get the keycodes of > the buttons and then bind them to whatever action > you want. > > Blu. The program is "showkeys". As for making it a macro, the only really free-form way I found was binding a key to Keyboard_Signal and then defining the action in inittab. Unfortunately, this limits to one user-defined key. Has anyone else figured out a better way to do this stuff? __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
