Opened 2 years ago

Last modified 6 weeks ago

#1532 new enhancement

GUI For "Remapping Key Assignments and Other Input Gestures"

Reported by: ateu Owned by:
Priority: minor Milestone:
Component: GUI Version: development
Keywords: Cc:
Operating system: Blocked by:
Blocking:

Description

Hello
Now nvda allows to do this changes manually, I think you have all the tools and you can easily create a menu iten for this option.
So all the users will enjoy it.

Change History (5)

comment:1 Changed 2 years ago by jteh

Unfortunately, this is not at all easy, as it needs to search for commands in all currently loaded modules and then determine which of those are matched by user and locale gesture maps. There is currently no efficient way to do this. Aside from this, command names and module names aren't currently user friendly or translatable, which needs to be done before a GUI can be considered.

Good patches are of course welcome.

comment:2 Changed 3 months ago by camlorn

I saw that this came up again recently, and have been considering opening a ticket for this for some time. Both of my computers, both my Windows laptop and my Macbook with bootcamp have keys that do not work properly, because the keyboard fails to recognize the keystroke combination altogether, so I'm going to assume that this isn't as rare as we would hope. The current option for modifying keystrokes is very, very technical; while I can complete it, I doubt someone newer to NVDA could. Also, it requires that you be able to obtain the name of the key, one way or another; the user guide only offers one option unless I'm missing a section: be able to actually press the key in the first place. I am lucky enough to have an external keyboard, but again, I imagine that many do not.

Even if this ignores add-ons, there really needs to be a way to do this without going through the cumbersome steps that the user guide says one must take. I am going to leave implementation suggestions to those qualified to actually usefully talk about them, as I have no idea how NVDA handles this, but it really does need to happen at some point. There is the option of maintaining a complete list of nvda keystrokes with names, but this seems unwise, at least to me.

comment:3 Changed 3 months ago by jteh

The fact that this needs to be done is not in question. Unfortunately, it's extremely difficult to implement and would probably require weeks of implementation time that we don't currently have given other priorities.

I assume you mean you need to be able to press the key to get the name of the command you want to remap? You don't need the name of the key itself.

comment:4 Changed 3 months ago by camlorn

Yes, that's what I meant. My estimate was not weeks, to be quite honest. I saw the first comment and assume that this was just sort of considered to be not worth it. I didn't realize it would take that long.

comment:5 Changed 6 weeks ago by nvdakor

Hi,
I and Beqa are trying to come up with a parsing algorithm (the first step to solving this ticket). Currently, Beqa is investigating how Orca does this.

Note: See TracTickets for help on using tickets.