Topics

NVDA focus problem.


John Isige
 

Hi all. I've noticed this for a couple of versions of both NVDA and Windows 10. When I switch windows with alt-tab, it seems like NVDA doesn't get full focus. For example, suppose I'm listening to a track, so I have two windows open, a Windows Explorer window with files, and Foobar 2000, or Winamp, or whatever media player I'm using. I want to alt-tab, let's say to turn repeat on or off or to see how much time remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the window. For instance, right now if I play a song and alt-tab to Winamp's window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But if I read the window title with NVDA-t, it says "explorer". The title is read correctly with alt-tab, but when I release alt-tab, I seem to be both in the window, and not in the window, as it were. The commands for the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something? In theory mine's set to 1024/768, unless Windows changed it after an update. BTW this gets fixed if I alt-tab back to another window, release alt-tab until that window comes up, and then alt-tab back to the other window, Foobar or whatever. When I do that it reads like it should and NVDA commands work and all. That's nothing earth-shattering of course, but it is fairly annoying, since it happens on a regular basis.


George McCoy <slr1bpz@...>
 

Hi John,

I have the same problem. You have described it perfectly. It certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message-----
From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the
window. For instance, right now if I play a song and alt-tab to Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But
if I read the window title with NVDA-t, it says "explorer". The title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window, release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.


Kenny Peyattt jr.
 

I am thinking about getting one of those laptops. Is it a touch screen or doe it just have a regular screen.
Kenny Peyatt jr.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of George McCoy
Sent: Saturday, July 14, 2018 3:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA focus problem.

Hi John,

I have the same problem. You have described it perfectly. It certainly is
annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message-----
From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the
window. For instance, right now if I play a song and alt-tab to Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But
if I read the window title with NVDA-t, it says "explorer". The title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window, release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.


Richard Wells
 

I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and get it that way. Of course, you should back up your registry before making this change, though I have modified several Windows 10 computers with this. Again, this advice is free and you get what you pay for.

On 7/14/2018 2:42 PM, George McCoy wrote:
   Hi John,

I have the same problem.  You have described it perfectly.  It certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the
window. For instance, right now if I play a song and alt-tab to Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But
if I read the window title with NVDA-t, it says "explorer". The title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window, release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.






John Isige
 

What does it do? I mean I accept that it's solved the problem for you,
but why?

On 7/14/2018 18:22, Richard Wells wrote:
I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open
https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
get it that way. Of course, you should back up your registry before
making this change, though I have modified several Windows 10
computers with this. Again, this advice is free and you get what you
pay for.


On 7/14/2018 2:42 PM, George McCoy wrote:
   Hi John,

I have the same problem.  You have described it perfectly.  It
certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the
window. For instance, right now if I play a song and alt-tab to Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But
if I read the window title with NVDA-t, it says "explorer". The title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window, release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.








Richard Wells
 

John: It returned the ALT+TAB function to the way it worked in previous Windows revisions.

On 7/14/2018 9:06 PM, John Isige wrote:
What does it do? I mean I accept that it's solved the problem for you,
but why?


On 7/14/2018 18:22, Richard Wells wrote:
I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open
https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
get it that way. Of course, you should back up your registry before
making this change, though I have modified several Windows 10
computers with this. Again, this advice is free and you get what you
pay for.


On 7/14/2018 2:42 PM, George McCoy wrote:
   Hi John,

I have the same problem.  You have described it perfectly.  It
certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't read the
window. For instance, right now if I play a song and alt-tab to Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to play. But
if I read the window title with NVDA-t, it says "explorer". The title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window, release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.










John Isige
 

Cool. But what are the differences, do you know? I mean, if it weren't
for this issue, I'd have no idea that they changed anything. It appears,
on the surface, to work exactly as it always has.

On 7/14/2018 21:19, Richard Wells wrote:
John: It returned the ALT+TAB function to the way it worked in
previous Windows revisions.


On 7/14/2018 9:06 PM, John Isige wrote:
What does it do? I mean I accept that it's solved the problem for you,
but why?


On 7/14/2018 18:22, Richard Wells wrote:
I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open
https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
get it that way. Of course, you should back up your registry before
making this change, though I have modified several Windows 10
computers with this. Again, this advice is free and you get what you
pay for.


On 7/14/2018 2:42 PM, George McCoy wrote:
   Hi John,

I have the same problem.  You have described it perfectly. It
certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't
read the
window. For instance, right now if I play a song and alt-tab to
Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
play. But
if I read the window title with NVDA-t, it says "explorer". The
title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands
for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or
something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window,
release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.












Brian's Mail list account <bglists@...>
 

I've not heard of this either. Is it perhaps a mistake when they removed the next feature of changing alt tab etc so you can have lots of sessions instead of 1?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "John Isige" <gwynn@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, July 15, 2018 6:51 AM
Subject: Re: [nvda] NVDA focus problem.


Cool. But what are the differences, do you know? I mean, if it weren't
for this issue, I'd have no idea that they changed anything. It appears,
on the surface, to work exactly as it always has.


On 7/14/2018 21:19, Richard Wells wrote:
John: It returned the ALT+TAB function to the way it worked in
previous Windows revisions.


On 7/14/2018 9:06 PM, John Isige wrote:
What does it do? I mean I accept that it's solved the problem for you,
but why?


On 7/14/2018 18:22, Richard Wells wrote:
I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open
https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
get it that way. Of course, you should back up your registry before
making this change, though I have modified several Windows 10
computers with this. Again, this advice is free and you get what you
pay for.


On 7/14/2018 2:42 PM, George McCoy wrote:
Hi John,

I have the same problem. You have described it perfectly. It
certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't
read the
window. For instance, right now if I play a song and alt-tab to
Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
play. But
if I read the window title with NVDA-t, it says "explorer". The
title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands
for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or
something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window,
release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.













Felix G.
 

Hello!
This may very well be related to an issue I previously reported:
Focus tracking seems to have degraded at some point, speculatively speaking, as the result of UIA coming to replace MSAA more and more. A fix isn't in sight as it seems to be hard to reproduce for those well versed in the details of NVDA's architecture. So I suggest that anyone affected comment there also. The more data, the more likely a reproduction.
The emerging pattern seems to be that it happens much less frequently on very fast machines, and more frequently in the presence of cpu-intensive processes, indicating a timing issue leading to dropped events.
Best,
Felix

Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> schrieb am So., 15. Juli 2018 um 10:23 Uhr:

I've not heard of this either. Is it perhaps a mistake when they removed the
next feature of changing alt tab etc so you can have lots of sessions
instead of 1?
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "John Isige" <gwynn@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, July 15, 2018 6:51 AM
Subject: Re: [nvda] NVDA focus problem.


Cool. But what are the differences, do you know? I mean, if it weren't
for this issue, I'd have no idea that they changed anything. It appears,
on the surface, to work exactly as it always has.


On 7/14/2018 21:19, Richard Wells wrote:
> John: It returned the ALT+TAB function to the way it worked in
> previous Windows revisions.
>
>
> On 7/14/2018 9:06 PM, John Isige wrote:
>> What does it do? I mean I accept that it's solved the problem for you,
>> but why?
>>
>>
>> On 7/14/2018 18:22, Richard Wells wrote:
>>> I cured this by adding the following key and value to my registry:
>>>
>>> [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
>>> "AltTabSettings"=dword:00000001
>>>
>>> If you just want a .reg file for merging this into your registry, open
>>> https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
>>> get it that way. Of course, you should back up your registry before
>>> making this change, though I have modified several Windows 10
>>> computers with this. Again, this advice is free and you get what you
>>> pay for.
>>>
>>>
>>> On 7/14/2018 2:42 PM, George McCoy wrote:
>>>> Hi John,
>>>>
>>>> I have the same problem. You have described it perfectly. It
>>>> certainly is annoying.
>>>>
>>>> I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.
>>>>
>>>> George
>>>>
>>>> -----Original Message----- From: John Isige
>>>> Sent: Saturday, July 14, 2018 12:46 PM
>>>> To: nvda@nvda.groups.io
>>>> Subject: [nvda] NVDA focus problem.
>>>>
>>>> Hi all. I've noticed this for a couple of versions of both NVDA and
>>>> Windows 10. When I switch windows with alt-tab, it seems like NVDA
>>>> doesn't get full focus. For example, suppose I'm listening to a track,
>>>> so I have two windows open, a Windows Explorer window with files, and
>>>> Foobar 2000, or Winamp, or whatever media player I'm using. I want to
>>>> alt-tab, let's say to turn repeat on or off or to see how much time
>>>> remains in the file.
>>>>
>>>>
>>>> If I do that, it seems like the commands work, but NVDA doesn't
>>>> read the
>>>> window. For instance, right now if I play a song and alt-tab to
>>>> Winamp's
>>>> window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
>>>> play. But
>>>> if I read the window title with NVDA-t, it says "explorer". The
>>>> title is
>>>> read correctly with alt-tab, but when I release alt-tab, I seem to be
>>>> both in the window, and not in the window, as it were. The commands
>>>> for
>>>> the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
>>>> or Foobar to get the remaining time, don't.
>>>>
>>>>
>>>> Is there a way to fix this? A different screen resolution or
>>>> something?
>>>> In theory mine's set to 1024/768, unless Windows changed it after an
>>>> update. BTW this gets fixed if I alt-tab back to another window,
>>>> release
>>>> alt-tab until that window comes up, and then alt-tab back to the other
>>>> window, Foobar or whatever. When I do that it reads like it should and
>>>> NVDA commands work and all. That's nothing earth-shattering of course,
>>>> but it is fairly annoying, since it happens on a regular basis.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>








Richard Wells
 

To a sighted person, the ALT+TAB looks completely different and has a completely new look and feel. Sadly, it also confuses screen access technology.

On 7/15/2018 12:51 AM, John Isige wrote:
Cool. But what are the differences, do you know? I mean, if it weren't
for this issue, I'd have no idea that they changed anything. It appears,
on the surface, to work exactly as it always has.


On 7/14/2018 21:19, Richard Wells wrote:
John: It returned the ALT+TAB function to the way it worked in
previous Windows revisions.


On 7/14/2018 9:06 PM, John Isige wrote:
What does it do? I mean I accept that it's solved the problem for you,
but why?


On 7/14/2018 18:22, Richard Wells wrote:
I cured this by adding the following key and value to my registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"AltTabSettings"=dword:00000001

If you just want a .reg file for merging this into your registry, open
https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
get it that way. Of course, you should back up your registry before
making this change, though I have modified several Windows 10
computers with this. Again, this advice is free and you get what you
pay for.


On 7/14/2018 2:42 PM, George McCoy wrote:
   Hi John,

I have the same problem.  You have described it perfectly. It
certainly is annoying.

I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.

George

-----Original Message----- From: John Isige
Sent: Saturday, July 14, 2018 12:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA focus problem.

Hi all. I've noticed this for a couple of versions of both NVDA and
Windows 10. When I switch windows with alt-tab, it seems like NVDA
doesn't get full focus. For example, suppose I'm listening to a track,
so I have two windows open, a Windows Explorer window with files, and
Foobar 2000, or Winamp, or whatever media player I'm using. I want to
alt-tab, let's say to turn repeat on or off or to see how much time
remains in the file.


If I do that, it seems like the commands work, but NVDA doesn't
read the
window. For instance, right now if I play a song and alt-tab to
Winamp's
window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
play. But
if I read the window title with NVDA-t, it says "explorer". The
title is
read correctly with alt-tab, but when I release alt-tab, I seem to be
both in the window, and not in the window, as it were. The commands
for
the program work, but NVDA things, e.g. hitting ctrl-shift-r in Winamp
or Foobar to get the remaining time, don't.


Is there a way to fix this? A different screen resolution or
something?
In theory mine's set to 1024/768, unless Windows changed it after an
update. BTW this gets fixed if I alt-tab back to another window,
release
alt-tab until that window comes up, and then alt-tab back to the other
window, Foobar or whatever. When I do that it reads like it should and
NVDA commands work and all. That's nothing earth-shattering of course,
but it is fairly annoying, since it happens on a regular basis.














Felix G.
 

Hi!
On the other hand, it's been out there long enough for screen reading technology to catch up, unless the new way still has inconsistencies, of course. Then it would be Microsoft's turn to fix those in an update.
It is a fact, however, that focus isn't just lost when alt+tabbing but for instance also in many cases when a new window is opened by activating a desktop icon. So alt+tab may be part of the story but it is not comprehensive. In the worst case, alt+tab may be a distraction from a much more basic problem, which just so happens to become exacerbated when alt+tabbing.
Best,
Felix

Richard Wells <richwels@...> schrieb am So., 15. Juli 2018 um 15:31 Uhr:

To a sighted person, the ALT+TAB looks completely different and has a
completely new look and feel. Sadly, it also confuses screen access
technology.


On 7/15/2018 12:51 AM, John Isige wrote:
> Cool. But what are the differences, do you know? I mean, if it weren't
> for this issue, I'd have no idea that they changed anything. It appears,
> on the surface, to work exactly as it always has.
>
>
> On 7/14/2018 21:19, Richard Wells wrote:
>> John: It returned the ALT+TAB function to the way it worked in
>> previous Windows revisions.
>>
>>
>> On 7/14/2018 9:06 PM, John Isige wrote:
>>> What does it do? I mean I accept that it's solved the problem for you,
>>> but why?
>>>
>>>
>>> On 7/14/2018 18:22, Richard Wells wrote:
>>>> I cured this by adding the following key and value to my registry:
>>>>
>>>> [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
>>>> "AltTabSettings"=dword:00000001
>>>>
>>>> If you just want a .reg file for merging this into your registry, open
>>>> https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
>>>> get it that way. Of course, you should back up your registry before
>>>> making this change, though I have modified several Windows 10
>>>> computers with this. Again, this advice is free and you get what you
>>>> pay for.
>>>>
>>>>
>>>> On 7/14/2018 2:42 PM, George McCoy wrote:
>>>>>    Hi John,
>>>>>
>>>>> I have the same problem.  You have described it perfectly. It
>>>>> certainly is annoying.
>>>>>
>>>>> I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.
>>>>>
>>>>> George
>>>>>
>>>>> -----Original Message----- From: John Isige
>>>>> Sent: Saturday, July 14, 2018 12:46 PM
>>>>> To: nvda@nvda.groups.io
>>>>> Subject: [nvda] NVDA focus problem.
>>>>>
>>>>> Hi all. I've noticed this for a couple of versions of both NVDA and
>>>>> Windows 10. When I switch windows with alt-tab, it seems like NVDA
>>>>> doesn't get full focus. For example, suppose I'm listening to a
>>>>> track,
>>>>> so I have two windows open, a Windows Explorer window with files, and
>>>>> Foobar 2000, or Winamp, or whatever media player I'm using. I want to
>>>>> alt-tab, let's say to turn repeat on or off or to see how much time
>>>>> remains in the file.
>>>>>
>>>>>
>>>>> If I do that, it seems like the commands work, but NVDA doesn't
>>>>> read the
>>>>> window. For instance, right now if I play a song and alt-tab to
>>>>> Winamp's
>>>>> window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
>>>>> play. But
>>>>> if I read the window title with NVDA-t, it says "explorer". The
>>>>> title is
>>>>> read correctly with alt-tab, but when I release alt-tab, I seem to be
>>>>> both in the window, and not in the window, as it were. The commands
>>>>> for
>>>>> the program work, but NVDA things, e.g. hitting ctrl-shift-r in
>>>>> Winamp
>>>>> or Foobar to get the remaining time, don't.
>>>>>
>>>>>
>>>>> Is there a way to fix this? A different screen resolution or
>>>>> something?
>>>>> In theory mine's set to 1024/768, unless Windows changed it after an
>>>>> update. BTW this gets fixed if I alt-tab back to another window,
>>>>> release
>>>>> alt-tab until that window comes up, and then alt-tab back to the
>>>>> other
>>>>> window, Foobar or whatever. When I do that it reads like it should
>>>>> and
>>>>> NVDA commands work and all. That's nothing earth-shattering of
>>>>> course,
>>>>> but it is fairly annoying, since it happens on a regular basis.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>





Quentin Christensen
 

Are you using alt+tab or windows+tab?  Windows+tab has definitely changed a lot with the timeline etc (although NVDA still works with it), but alt+tab looks and behaves much like it ever has.  I can't reproduce the title bar reading "explorer" myself (either with the latest alpha build or with NVDA 2018.2.1, both on Windows 10 fast insider), but perhaps if someone can, could you try pressing NVDA+F1 to open the log and give information about where the focus is, and if you copy the whole thing and send it to me in an email to info@... I can have a look.

For those having problems, what machine are you running and what other software?  EG, someone mentioned using a HP laptop - they are notorious for filling the notification area with their own little programs and utilities - as all laptop manufacturers do - but at times, some of those can have invisible windows which can cause interesting bugs like this (and since I'm using a vanilla desktop, it would explain why I can't repro it).  Also are you using any anti-virus software other than Windows defender?  That can often cause issues as well.

Kind regards

Quentin.

On Mon, Jul 16, 2018 at 4:04 PM, Felix G. <constantlyvariable@...> wrote:
Hi!
On the other hand, it's been out there long enough for screen reading technology to catch up, unless the new way still has inconsistencies, of course. Then it would be Microsoft's turn to fix those in an update.
It is a fact, however, that focus isn't just lost when alt+tabbing but for instance also in many cases when a new window is opened by activating a desktop icon. So alt+tab may be part of the story but it is not comprehensive. In the worst case, alt+tab may be a distraction from a much more basic problem, which just so happens to become exacerbated when alt+tabbing.
Best,
Felix

Richard Wells <richwels@...> schrieb am So., 15. Juli 2018 um 15:31 Uhr:
To a sighted person, the ALT+TAB looks completely different and has a
completely new look and feel. Sadly, it also confuses screen access
technology.


On 7/15/2018 12:51 AM, John Isige wrote:
> Cool. But what are the differences, do you know? I mean, if it weren't
> for this issue, I'd have no idea that they changed anything. It appears,
> on the surface, to work exactly as it always has.
>
>
> On 7/14/2018 21:19, Richard Wells wrote:
>> John: It returned the ALT+TAB function to the way it worked in
>> previous Windows revisions.
>>
>>
>> On 7/14/2018 9:06 PM, John Isige wrote:
>>> What does it do? I mean I accept that it's solved the problem for you,
>>> but why?
>>>
>>>
>>> On 7/14/2018 18:22, Richard Wells wrote:
>>>> I cured this by adding the following key and value to my registry:
>>>>
>>>> [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
>>>> "AltTabSettings"=dword:00000001
>>>>
>>>> If you just want a .reg file for merging this into your registry, open
>>>> https://www.dropbox.com/s/ju6rmd6go0pyune/AltTabSettings.reg?dl=1 and
>>>> get it that way. Of course, you should back up your registry before
>>>> making this change, though I have modified several Windows 10
>>>> computers with this. Again, this advice is free and you get what you
>>>> pay for.
>>>>
>>>>
>>>> On 7/14/2018 2:42 PM, George McCoy wrote:
>>>>>    Hi John,
>>>>>
>>>>> I have the same problem.  You have described it perfectly. It
>>>>> certainly is annoying.
>>>>>
>>>>> I'm running windows 10 pro 64 bit on a HP Elitebook 8440W.
>>>>>
>>>>> George
>>>>>
>>>>> -----Original Message----- From: John Isige
>>>>> Sent: Saturday, July 14, 2018 12:46 PM
>>>>> To: nvda@nvda.groups.io
>>>>> Subject: [nvda] NVDA focus problem.
>>>>>
>>>>> Hi all. I've noticed this for a couple of versions of both NVDA and
>>>>> Windows 10. When I switch windows with alt-tab, it seems like NVDA
>>>>> doesn't get full focus. For example, suppose I'm listening to a
>>>>> track,
>>>>> so I have two windows open, a Windows Explorer window with files, and
>>>>> Foobar 2000, or Winamp, or whatever media player I'm using. I want to
>>>>> alt-tab, let's say to turn repeat on or off or to see how much time
>>>>> remains in the file.
>>>>>
>>>>>
>>>>> If I do that, it seems like the commands work, but NVDA doesn't
>>>>> read the
>>>>> window. For instance, right now if I play a song and alt-tab to
>>>>> Winamp's
>>>>> window, i can hit keys and they work, e.g. 'v' to stop, 'x' to
>>>>> play. But
>>>>> if I read the window title with NVDA-t, it says "explorer". The
>>>>> title is
>>>>> read correctly with alt-tab, but when I release alt-tab, I seem to be
>>>>> both in the window, and not in the window, as it were. The commands
>>>>> for
>>>>> the program work, but NVDA things, e.g. hitting ctrl-shift-r in
>>>>> Winamp
>>>>> or Foobar to get the remaining time, don't.
>>>>>
>>>>>
>>>>> Is there a way to fix this? A different screen resolution or
>>>>> something?
>>>>> In theory mine's set to 1024/768, unless Windows changed it after an
>>>>> update. BTW this gets fixed if I alt-tab back to another window,
>>>>> release
>>>>> alt-tab until that window comes up, and then alt-tab back to the
>>>>> other
>>>>> window, Foobar or whatever. When I do that it reads like it should
>>>>> and
>>>>> NVDA commands work and all. That's nothing earth-shattering of
>>>>> course,
>>>>> but it is fairly annoying, since it happens on a regular basis.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>







--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Pranav Lal
 

Richard,

What does this setting do?

Pranav


 

On Sun, Jul 15, 2018 at 09:31 AM, Richard Wells wrote:
ALT+TAB looks completely different and has a completely new look and feel.
-
As a sighted person, I regret to inform you that this is incorrect.  There are, perhaps, subtle differences, but not anything that would make anyone say, "Hey, what in the heck is going on here?  This looks and behaves nothing like I was used to?"
 
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde