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
improving keyboard layout managing #64
Comments
Comment 1 by mdcurran on 2008-04-30 05:20 |
Comment 2 by mdcurran on 2008-11-17 22:44 |
Comment 3 by mdcurran on 2008-11-17 22:59 |
Comment 4 by mdcurran on 2008-11-17 23:00 |
Comment 5 by aleksey_s on 2008-11-22 22:00 |
Comment 6 by jteh on 2009-05-18 05:27 |
Comment 7 by MHameed on 2013-02-25 19:49 |
Comment 8 by jteh (in reply to comment 7) on 2013-02-26 06:05
Imo, this isn't a good idea. I recognise the potential for clashes, but not having any bindings at all is very unfriendly for users. There could be a huge number of commands that need to be bound. There is definitely a need for a GUI to manage custom gesture binding. This is covered by #1532, though implementing it is very complicated due to the hugely dynamic way NVDA handles bindings. |
Comment 9 by nvdakor on 2014-07-25 12:53 |
Comment 10 by jteh on 2014-07-28 06:45 |
Reported by aleksey_s on 2008-04-09 18:24
when nvda loads keyboard layout, it must check and log how many scripts were not mapped, and probably log their names too, to be easier for layout creators to update their files.
also some combobox needed for user to can change keyboard layout with out editing nvda.ini file. nvda might search *.kbd files and put to combobox all diferent parts after underline. so keyboard layouts might be named e.g. laptop, mick's laptop etc.
The text was updated successfully, but these errors were encountered: