Active Topics

 


Reply
Thread Tools
Posts: 71 | Thanked: 6 times | Joined on Jan 2006
#11
How about disabling key repeat in kbdd? automatically sending a 'keyup' command after 'keydn' for all keys? surely something could be changed in kbdd. The source code is pretty easy to understand. Makes me wonder why the dev didn't write a 'debugprint' function.
 
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#12
Originally Posted by spiderx View Post
How about disabling key repeat in kbdd?
There are other tools for that but yes it could be added to kbdd too (together with kitchen sink ;-) In initfs there is evrepeat that might do what you want. Try as root this
Code:
chroot /mnt/initfs evrepeat
This could be added to btkbd script if some variable with preferred repeat rate is set in btkbd.conf.
Originally Posted by spiderx View Post
automatically sending a 'keyup' command after 'keydn' for all keys?
Ugly hack, it is easier to simply turn it off in linux kernel if you prefer no key repeat.
Originally Posted by spiderx View Post
The source code is pretty easy to understand. Makes me wonder why the dev didn't write a 'debugprint' function.
Yes, it is pretty simple. It is so simple you can actually add features mentioned above if you feel kbdd is right place for them. Or even rewrite it from scratch with bluetooth specifically in mind (might be good idea). kbdd was not done by me, I just recompiled it for maemo and added one my keyboard and few done by others. So far I wanted to minimize other changes since in such case it would be better to really start from scratch.

There is -d option which does print sent/received key codes. Try to run kbdd executable to see help. You can also set DEBUG=yes in btkbd.conf to have the debug output enabled and redirected to /tmp/kbdd.log
 
Reply


 
Forum Jump


All times are GMT. The time now is 17:00.