Re: NVDA say all command not working.
Having Laptop keyboard layout selected does not preclude the use of Insert key as the NVDA modifier key it Just enables the use of the Caps lock key as a Modifier Key and re-assigns the key commands that are assigned to the key comprised in the Num pad as most laptops don’t have a numpad.
In NVDA and also JAWS if you select laptop keyboard layout even with a desktop keyboard you can then use either Insert or Caps lock as your modifier key and either the desktop or Laptop key commands, which can actually be quite helpful with some of the more acrobatic keyboard commans (where smaller hands or where dexterity is an issue.)
Although the laptop keyboard does have a numpad and an insert key, I choose to leave set to laptop in consultation with the user.
I thank you for your advise and input into this issue.
From: firstname.lastname@example.org <email@example.com>
On Behalf Of Gene
If a numpad is present, why did you change the setting to laptop? Laptop keyboard layout doesn't mean you have to use it with a desktop. It is intended to be used with any keyboard with a numpad or if you have a USB numpad connected to a computer that doesn't have a numpad. The laptop keyboard layout is intended to be used on computers without numpads and those are usually laptops, which is why it is named laptop layout.
Set the keyboard back to desktop layout. If you don't, the command the person wants to use won't work or leave at desktop, if it is already there.
----- Original Message -----
Hi Joseph and list
On Friday I was able to re-contact my client to continue troubleshooting this issue. At that time I was able to use team viewer to remote into his system. During this contact and access to his system I was able to;
1 Establish that he is in fact using a laptop keyboard that has a Numpad.
2 NVDA setting show that desktop keyboard layout was selected now altered to reflect Laptop keyboard.
3 He has no add-ons installed according to the add-on manager in NVDA
4 He is using Windows One core synth with Microsoft David voice.
5 Restarting NVDA with add-ons disabled does indeed resolve the problem.
6 Resetting to NVDA to factory defaults had no impact in the issue when running NVDA normally
At this point the remote connection with team viewer became very laggy and un-usable and my client had to attend to other matters. So we had to abandon and will continue on Monday or Tuesday at which time I endeavour to verify NVDA and Windows version and build details.
I thanks everyone for their assistance an contribution to this issue thus far offer my thanks and appreciation.
Is your client using any NVDA add-ons at the moment? If yes, it might be possible that a recent add-on update may have contributed to this problem. If it turns out add-ons might be to blame, have your client follow Gene’s advice of restarting NVDA with add-ons disabled and see if that makes a difference.
Thank you so much the warm welcome and for taking the time to assist with this issue.
I confirmed they are using a desktop keyboard and believe that their NVDA config is set to desktop keyboard but I will contact and confirm this and relay your message.
Thank you again for your time and assistance with this issue.
First, welcome to NVDA users list.
If you don’t mind, can you pass on the following message to your client please:
This is Joseph Lee, one of the developers of NVDA screen reader.
I heard from a person you work with that say all command (NVDA+down arrow) isn’t working for you all the way. This might be caused by one or more of the following:
Hope this helps.
I have a client who is using the latest version of NVDA on a Windows 10 Laptop with Office 2016.
The client is reasonably proficient with using NVDA and reports that when attempting to use the “SAY ALL” ( INSERT+DOWN ARROW ) in word, Outlook, notepad various other programs, that the command fails to read to the end of the Page or Document from the currently focused point. The client states it will usually read to the end of the line, sentence, or paragraph and that repeating the command will prompt NVDA to continue reading but again not to the end as expected.
This issue is reported to me as having been occurring for approximately 4 to 6 weeks, So has survived several system reboots. I have ensured via phone that the client is using the latest version and currently there are no updates available for the client.
I have been unable to reproduce this issue on a test system or my work system with the latest version or the previous versions of NVDA. Reset to factory defaults would be the next obvious step but I would like to know if this is a known issue or if there is some way of resolving this without a reset to defaults.
Any advice or assistance is greatly appreciated.