Skip to content
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

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 10 comments
Closed

improving keyboard layout managing #64

nvaccessAuto opened this issue Jan 1, 2010 · 10 comments

Comments

@nvaccessAuto
Copy link

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.

@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2008-04-30 05:20
Added support for selecting keyboard layout from the keyboard settings dialog in svn r1989. See trac ticket #60 for more info. In regards to logging bad key names, this shouldn't be too hard. Though I think exceptions are already log for any script name that doesn't exist, though I guess this may b a bit unclear as to what that really means.

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2008-11-17 22:44
Seems that NVDA does log any key binding that failed because the script did not exist. So I think we're done with this ticket.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2008-11-17 22:59
NVDA is much different to other screen readers in its dictionary implementation. Ordering of entries is very important. If we ordered by comment or anything else other than the actual file order, then the user may be adding entries that may not work because they could be overridden by ones that appear above their entry.

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2008-11-17 23:00
Please ignore the last comment, my mystake.

@nvaccessAuto
Copy link
Author

Comment 5 by aleksey_s on 2008-11-22 22:00
i requested logging script names which exists but not mapped to key as well as warning when one keystroke is used in different scripts in same appmodule. this isn't yet implemented.
Changes:
State: reopened

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2009-05-18 05:27
Changes:
Milestone changed from 0.6 to None

@nvaccessAuto
Copy link
Author

Comment 7 by MHameed on 2013-02-25 19:49
gestures manager:
With more addons being created and being circulated, the likelyhood of clashing shortcut keys is increasing.
Would it be possible for an appmodule/globalModule to register its functions (without any assigned keys), then the user could browse the functionality and the unassigned/assigned/reassign keys.
This would be simular to Orca keybindings, i.e. a treeview for each group, when the group is expanded one could browse the available functionality, and reset to default, reassign to a different key etc.
This would also aid functionality/shortcut discoverability.

@nvaccessAuto
Copy link
Author

Comment 8 by jteh (in reply to comment 7) on 2013-02-26 06:05
Replying to MHameed:

Would it be possible for an appmodule/globalModule to register its functions (without any assigned keys)

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.

@nvaccessAuto
Copy link
Author

Comment 9 by nvdakor on 2014-07-25 12:53
Hi,
Now that #1532 has been implemented, I think this ticket could be closed unless there are issues to be solved.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 10 by jteh on 2014-07-28 06:45
This isn't really relevant any more, since we don't use kbd files now and we also have #1532.
Changes:
Added labels: invalid
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant