New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhanced input gesture mapping #194
Comments
Comment 1 by jteh on 2008-10-11 12:16 Another option might be to provide a set of key bindings which are common to all keyboard layouts; i.e. a "common" keyboard layout. This would include keys such as NVDA+t, NVDA+f12, NVDA+upArrow, etc. which aren't likely to need to change in different layouts. Out of interest, what is the use case for having different layouts here? There's obviously the laptop layout, but what other layouts are users creating? |
Comment 2 by Bernd (in reply to comment 1) on 2009-02-22 02:32
I think Users will maybe write different maps if they have a program with an key command they need often so they don't have to pass the next key command to the aplication. |
Comment 3 by jteh on 2009-05-01 01:23 |
Comment 6 by jteh on 2010-03-19 02:55
Note that kb:common is common to both desktop and laptop layouts. |
Comment 7 by aleksey_s (in reply to comment 6) on 2010-03-20 06:40
Does it allow to have user customized mappings? e.g. where not all bindings are redefined but only a few of them.
Certainly. |
Comment 8 by jteh (in reply to comment 7) on 2010-03-20 12:45
Yes. There will be a single user map where users can define whatever gesture mappings they wish. |
Comment 9 by jteh on 2010-10-22 06:40
Changes: |
Comment 10 by jteh on 2010-10-27 01:06 App modules no longer have external key map files. Instead, gestures are bound in the app module. There will be locale and user external gesture maps to allow internal bindings to be overridden. |
Comment 11 by jteh on 2010-11-26 05:04 |
Reported by aleksey_s on 2008-10-11 06:38
Currently it is uncomfortable to maintain more than one nvda .kbd files, becouse you need add all new written scripts to all .kbd files. thus with oficially distributed key maps it isn't so difficult, with maps which have one user it isn't possible. this must be rewoked somehow.
may be as follow:
in .kbd files pairs of settings must be no keystroke=script, but script=keystroke. so we have main kbd file (now it is desktop), and how many as one's need extending files. when loading new map, some script keystroke may be changed, and some not. ofcourse, main map file must be loaded first of all, and just it will have all assotiations, other may have redefine just some of them.
Blocked by #601
Blocking #810
The text was updated successfully, but these errors were encountered: