Mercurial > hg > index.fcgi > keynav-9pba
comparison README @ 0:ab8a496afb67
initial hg commit of my version of keynav
author | paulo@thepaulopc |
---|---|
date | Tue, 08 Sep 2009 22:45:57 -0700 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:c33a76935f42 |
---|---|
1 2008-05-06 | |
2 | |
3 This is Jordan Sissel's 'keynav', modified by Paulo Ang. | |
4 | |
5 http://www.semicomplete.com/projects/keynav | |
6 http://iacs5.ucsd.edu/~pbang/mouseless.htm | |
7 | |
8 Note that this is based on an earlier release of 'keynav', not the | |
9 latest 'xdotool' based code. | |
10 | |
11 | |
12 To build: | |
13 | |
14 Run 'xmkmf', then 'make keynav'. | |
15 | |
16 To run: | |
17 | |
18 Simply run 'keynav'. For a list of the default keys see 'config.h'. | |
19 | |
20 To configure keys: | |
21 | |
22 Modify 'config.h' and recompile. | |
23 | |
24 To configure even more: | |
25 | |
26 Modify 'keynav.c' and recompile. | |
27 | |
28 | |
29 Hints: | |
30 | |
31 It's faster to use the "diagonal" movement keys, since they split the | |
32 mouse area into four accessible parts, but the binary vi-keys is easier | |
33 when you're just starting out or fine-tuning a small area. | |
34 | |
35 A good tactic would be to use the diagonal keys until the point you want to | |
36 click on is exactly on the crosshairs (or the selection area is too small), | |
37 then just use vi-keys to hone in. | |
38 | |
39 The nine-grid mode is even faster than the regular four-grid mode. | |
40 Enable it by default by specifying '-n <num>' parameters to keynav, where | |
41 <num> is the number of moves before it automatically switches back to | |
42 four-grid mode. Or press Shift-[center]. But you may want to hold off on | |
43 using it until you get the hang of the four-grid mode first. | |
44 | |
45 You can have two instances of 'keynav' running simulataneously, as long as | |
46 they have different trigger keys. You may want to do this to be able to use | |
47 both home row keys and the numeric keypad to 'keynav', for example. | |
48 | |
49 | |
50 About the statistics: | |
51 | |
52 'keynav' outputs debug messages to stderr, and stats to stdout. Simply | |
53 redirect to taste. 'hits' are the number of keys you've hit, 'moves' are the | |
54 number of movements made, and 'clicks' are the number of mouseclicks | |
55 not including simple clicks (ie, clicks that don't end the movement mode). | |
56 | |
57 | |
58 If 'keynav' appears to hang: | |
59 | |
60 It's probably because of the drag mode, which can be buggy with some apps. | |
61 A click from your real mouse will probably restore keyboard control, where | |
62 you can kill 'keynav' and start it up again. |