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

Some commands not listed in the User Guide #954

Closed
nvaccessAuto opened this issue Oct 1, 2010 · 9 comments
Closed

Some commands not listed in the User Guide #954

nvaccessAuto opened this issue Oct 1, 2010 · 9 comments

Comments

@nvaccessAuto
Copy link

Reported by drein on 2010-10-01 16:51
KeyCommand NVDA+Control+f1 is not mentioned in the user manual and so it is not generated in the keycommand reference.

@nvaccessAuto
Copy link
Author

Comment 1 by orcauser on 2010-10-04 14:22
reading status line is also not listed.
switch between none/beep/speak letters when typing is also missing.

there are some others, but unfortunately i cant find the list that i made, if i do i will post here.
It would be good if someone could go through and check, and put them into their proper places.
I think it might be worth braking the string freeze on the userguide, because otherwise we would have a regression in the information provided to the user.

Thanks.

Jon

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2010-10-04 23:57
Changes:
Changed title from "command NVDA+Control+f1 is not listed in the command reference" to "Some commands not listed in the User Guide"
Milestone changed from None to 2010.3

@nvaccessAuto
Copy link
Author

Comment 3 by Bernd on 2010-11-04 21:14
Folowing keys are missing in the User Guide

NVDA+s=speechMode
NVDA+end=reportStatusLine
NVDA+numpadDivide=moveMouseToNavigatorObject
NVDA+numpadMultiply=moveNavigatorObjectToMouse
NVDA+f1=navigatorObject_devInfo
NVDA+shift+b=say_battery_status
NVDA+5=toggleReportDynamicContentChanges
NVDA+control+g=activateGeneralSettingsDialog
NVDA+control+s=activateSynthesizerDialog
NVDA+control+d=activateDocumentFormattingDialog
NVDA+control+z=activatePythonConsole
NVDA+c=reportClipboardText
NVDA+control+f2=test_navigatorDisplayModelText

@nvaccessAuto
Copy link
Author

Comment 4 by jteh (in reply to comment 3) on 2010-11-04 21:46
Replying to Bernd:

NVDA+s=speechMode

Confirmed. Probably should go in section 5.4: Basic Key Commands.

NVDA+end=reportStatusLine

Confirmed. Probably should go in section 6.1: Navigating with the System Focus.

NVDA+numpadDivide=moveMouseToNavigatorObject

NVDA+numpadMultiply=moveNavigatorObjectToMouse

Documented in section 6.6: Navigating with the Mouse.

NVDA+f1=navigatorObject_devInfo

NVDA+control+z=activatePythonConsole

These are development commands and don't really fit into any of the existing sections of the User Guide. They aren't really relevant to most users at all. We'll need to think about this.

NVDA+control+g=activateGeneralSettingsDialog

NVDA+control+s=activateSynthesizerDialog

NVDA+control+d=activateDocumentFormattingDialog

All documented in sub-sections of section 8.1: Preferences.

NVDA+shift+b=say_battery_status

NVDA+c=reportClipboardText

Confirmed. I think we should move NVDA+f12 and these two commands into a new section for reporting system information after Basic Key Commands.

NVDA+5=toggleReportDynamicContentChanges

Confirmed. Don't know where to put this one.

NVDA+control+f2=test_navigatorDisplayModelText

This one in particular is a test command and will probably be removed altogether eventually.

@nvaccessAuto
Copy link
Author

Comment 5 by Bernd (in reply to comment 4) on 2010-11-04 23:16
Replying to jteh:

Replying to Bernd:

NVDA+s=speechMode

Confirmed. Probably should go in section 5.4: Basic Key Commands.

NVDA+end=reportStatusLine

Confirmed. Probably should go in section 6.1: Navigating with the System Focus.

ok, I'd create a diff file so you can patch the user guide

NVDA+numpadDivide=moveMouseToNavigatorObject

NVDA+numpadMultiply=moveNavigatorObjectToMouse

Documented in section 6.6: Navigating with the Mouse.

hmm, I missed them somehow

NVDA+f1=navigatorObject_devInfo

NVDA+control+z=activatePythonConsole

These are development commands and don't really fit into any of the existing sections of the User Guide. They aren't really relevant to most users at all. We'll need to think about this.

Maybe this commands could go somewhere in section 9. There is allready a section for the python console.

NVDA+control+g=activateGeneralSettingsDialog

NVDA+control+s=activateSynthesizerDialog

NVDA+control+d=activateDocumentFormattingDialog

All documented in sub-sections of section 8.1: Preferences.

Yes, but aren't listed in the key commands file. I checked the source file but can''t find a mistake.

NVDA+shift+b=say_battery_status

NVDA+c=reportClipboardText

Confirmed. I think we should move NVDA+f12 and these two commands into a new section for reporting system information after Basic Key Commands.

ok, I'll do this with in my diff file.

NVDA+5=toggleReportDynamicContentChanges

Confirmed. Don't know where to put this one.

hmm, what about creating a setting in the object presentation settings? Maybe it could go in the general settings if we get more general settings.

NVDA+control+f2=test_navigatorDisplayModelText

This one in particular is a test command and will probably be removed altogether eventually.

ok, I just noted them whith the others.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh (in reply to comment 5) on 2010-11-04 23:31
Replying to Bernd:

These are development commands and don't really fit into any of the existing sections of the User Guide. They aren't really relevant to most users at all. We'll need to think about this.

Maybe this commands could go somewhere in section 9. There is allready a section for the python console.

True, though that section refers the user to the wiki article about the Python Console. My thought was that developer info would stay on the web site.

All documented in sub-sections of section 8.1: Preferences.

Yes, but aren't listed in the key commands file.

They are for me in the headings of the sections, just as they are in the User Guide.

NVDA+5=toggleReportDynamicContentChanges

Confirmed. Don't know where to put this one.

hmm, what about creating a setting in the object presentation settings?

Yeah, this is probably best, although I don't know if it really needs a setting. Please leave this one out for now.

Thanks.

@nvaccessAuto
Copy link
Author

Attachment user_guide.diff added by Bernd on 2010-11-27 12:33
Description:

@nvaccessAuto
Copy link
Author

Comment 8 by mdcurran on 2010-12-02 05:56
Committed as 565920d. A few small language changes were made. Thanks for the patch.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 9 by mdcurran on 2010-12-14 03:55
report dynamic content changes (NVDA+5) is now a proper config option in nvda.ini and the GUI. It has also now been appropriately mentioned in the user guide.
Done in 9b4f3bd

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

2 participants