Comment 1 by surfer0627 on 2013-10-17 03:57
Changes:
Changed title from "Added NVDA Shortcuts in NVDA Menu" to "Added NVDA Shortcuts to NVDA Menu"

Comment 2 by jteh on 2013-10-17 04:10
This definitely makes sense. The problem is that these shortcuts might have been reassigned by the user. There's no quick, efficient way for the code to determine the key associated with a single command because a command can be overridden at several different levels.

Comment 3 by surfer0627 on 2013-10-17 05:47
Changes:
Changed title from "Added NVDA Shortcuts to NVDA Menu" to "Added NVDA Shortcuts Information to NVDA Menu"

Comment 4 by surfer0627 (in reply to comment 2) on 2013-10-17 08:42
By creating this ticket, I hope that NVDA could provide more information for users.

FOr example:
‧Synthesizer...

expected: Synthesizer... (NVDA+control+s)

‧Document formatting...

expected: Document formatting... (NVDA+control+d)

‧Python console

expected: Python console (NVDA+control+z)

Thank you.

Replying to jteh:

This definitely makes sense. The problem is that these shortcuts might have been reassigned by the user. There's no quick, efficient way for the code to determine the key associated with a single command because a command can be overridden at several different levels.

Comment 5 by surfer0627 on 2013-10-29 02:17
Shortcut information:
‧Configuration Profiles (NVDA+control+p)

Comment 6 by jteh on 2013-10-29 02:33
I understand what you're requesting here. I explained in comment:2 why this can't be done at present: the user might reassign them and there's no quick way to get the current binding.

Comment 7 by surfer0627 (in reply to comment 6) on 2013-10-30 01:16
Replying to jteh:

Yes, I got the point: "the user might reassign them and there's no quick way to get the current binding."

Is it possible that we don't have to get the current binding?

We just provide some useful tips for users. In the defult settings, users could use these shortcuts.

Now, users could only get shortcut information from User Guide and Commands Quick Reference.

Comment 8 by surfer0627 on 2014-11-14 01:51
Shortcut information:

Logs information about the current navigator object (NVDA+f1)

I do not know the shortcut until I read the ticket #4439, comment2.

@jcsteh noted in #3584 (comment) that reassigned key bindings are programmatically difficult to retrieve efficiently. Since the requested feature makes a lot of sense to me too, and it is very much possible that novice NVDA users may remain unaware about the keystrokes assigned to these NVDA dialogs, I would like to request technical reconsideration of this ticket by developers. Also, quite a few NVDA.ini dialogs are being unified in a pull request by @LeonarddeR which may affect this issue in ways. Thus, all this needs to be taken into account while we try to evaluate the relevance of this ticket with respect to ongoing NVDA GUI work.

This is not an issue anymore with the new NVDA gui.

@LeonarddeR I think this can be closed.

Oh sorry I think I missunderstood the issue. So it is required to bring object shortcut information to the menu and the cathegories. The problem I see here is that shortcuts can be adjusted by translators for the menu items. This is indeed very good because people who cannot speak inglish are able to build easily a context between the shortcut and the menu items. Ofcourse if the translation is accurate.

But this could be acomplished for settings ccathegories at least.

@jcsteh how is this actually solved in Firefox? Because when you navigate through the menu you get i.e. ctrl+t for opening a new tab etc. Maybe the gestures for opening the settings cathegories should be excluded from the input dialog so that they cannot be changed. What do you think?