Hi Gavin,
Thanks very much for the fix, that worked.
David, that's very strange. I always thought the two screen readers
could coexist in harmony - they use two completely different reading
methods after all. I appear to be mistaken and I can only apologise for
causing you to put your system and/or QWS into a state of chaos. I
really hope you can get it back to a state of normality.
Cheers,
Damien.
On 30/08/2020 11:51 pm, Gavin Grundlingh wrote:
Hi Damien,
I've seen this, too. I have no idea why this problem comes up, but I did
find a fix for it. There are two methods to apply this fix.
1. If you have the Pro version of Windows 10, you can use the group
policy editor.
Press Windows+R, type "gpedit.msc" and press Enter.
In the tree view, navigate to "Local Group Policy > User Configuration >
Administrative Templates > Windows Components > File Explorer > Common
Open File Dialog."
Tab to the list, select "Hide the Common Places Bar" and press Enter.
In the dialog that comes up, press Alt+E to select the "Enabled" radio
button, then press Enter.
Close the group policy editor and restart your computer.
2. If you do not have Windows 10 Pro, or you prefer to get down and
dirty with the registry, you can use Registry Editor.
Press Windows+R, type "regedit" and press Enter.
In the tree view, navigate to
"Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies."
Press Alt+E to go to the Edit menu, press N to select New, and then
press K to select Key.
In the Key Name edit box, type "Comdlg32" and press Enter.
In the tree view, make sure your focus is on "Comdlg32," then tab to the
list.
Press Alt+E to go to the Edit menu, press N to select New, and then
press D to select DWORD (32-bit) Value.
In the Value Name edit box, type "NoPlacesBar" and press Enter.
In the list, arrow down to "NoPlacesBar" and press Enter.
In the Value Data edit box, type "1" and press Enter.
Close Registry Editor and restart your computer.
Hope this helps. Please let us know if it works for you.
Regards,
Gavin
On 30-Aug-20 20:10, Damien Garwood wrote:
Hi,
Are there any NVDA users on here? If so, have you had trouble with the
open/save-as dialogs in QWS at any point since November last year
(namely files and folders not reading in the browser list)?
I started having this after a Windows update (from Windows 10 1809 to
1909), but put it to one side in case it was some weird issue with my
four-year-old machine and some messy Windows garbleness. But it
doesn't seem to be...I'm getting the same behaviour on my new machine
(now running Windows 10 2004), as is a friend of mine who I'm
currently teaching to use it, also on a new machine.
Unfortunately, I've no idea what could be causing the issue; QWS is
using a standard Windows dialog box, which NVDA has absolutely no
trouble accessing in other programs. To make matters even more
confusing, Narrator works fine with the QWS dialogs.
I wrote to the NVDA list regarding this at the time it started but
noone could shed any light on the issue, and several subsequent
updates to NVDA and Windows don't seem to have fixed it.
In case anyone wants to test it, I'm using NVDA 2020.2 (although at
the time the problem started I was on 2019.2.1) and QWS 1.56.
Cheers.
Damien.
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see
http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see http://www.mail-archive.com/[email protected]
