search

nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.1k stars 634 forks source link

Delay of around 7 seconds when changing to application using configuration profiles other than normal #8032

Closed sjtaylor82 closed 6 years ago

sjtaylor82 commented 6 years ago

Example:

  1. Open Firefox
  2. Visit Configuration profiles from NVDA.
  3. Create a new profile called Web and assign it to the application.

When switching between Firefox and other applications, significant delays are encountered. This is true of any application for which a separate config profile is created, e.g. Microsoft Word. This behaviour has been observed in NExt and Master builds of NVDA this week. Behaviour does not occur NVDA 2017.4. Behaviour is present in NVDA 2018.1 RC1.

josephsl commented 6 years ago

Hi, what speech synthesizer and/or Windows version are you using? Also, is this FF58? Lastly, what about creating and switching to profiles for other apps (such as Notepad or Chrome)? Thanks.

From: sjtaylor82 [mailto:notifications@github.com] Sent: Thursday, February 22, 2018 9:21 PM To: nvaccess/nvda nvda@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [nvaccess/nvda] Delay of around 7 seconds when changing to application using configuration profiles other than normal (#8032)

Example:

  1. Open Firefox
  2. Visit Configuration profiles from NVDA.
  3. Create a new profile called Web and assign it to the application.

When switching between Firefox and other applications, significant delays are encountered. This is true of any application for which a separate config profile is created, e.g. Microsoft Word. This behaviour has been observed in NExt and Master builds of NVDA this week. Behaviour does not occur NVDA 2017.4. Behaviour is present in NVDA 2018.1 RC1.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8032 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkF896dGX-l7KoFDI_fXcFydfrvrFks5tXkrAgaJpZM4SQZkL .

LeonarddeR commented 6 years ago

Are you using a braille display by any chance?

sjtaylor82 commented 6 years ago

I certainly do intermittently, but Braille is currently set to No Braille.

On 23/02/2018 15:44, Leonard de Ruijter wrote:

Are you using a braille display by any chance?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8032#issuecomment-367915958, or mute the thread https://github.com/notifications/unsubscribe-auth/AYxk8tQct3XVcr4ft-xaiIi7X2Grp6Rvks5tXlAkgaJpZM4SQZkL.

michaelDCurran commented 6 years ago

If you Restart NVDA with add-ons disabled, do you still experience the delay?

sjtaylor82 commented 6 years ago

HI Mick, Yes I do.

However, I have just changed braille input from UEB grade 2, to grade 1, and back to grade 2 again, still set to no braille.

I no longer can replicate the issue!

Come to think of it, this only started after recently using a HIMS braille display

On 23/02/2018 15:49, Michael Curran wrote:

If you Restart NVDA with add-ons disabled, do you still experience the delay?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8032#issuecomment-367916632, or mute the thread https://github.com/notifications/unsubscribe-auth/AYxk8iHv8i02QqXkekIxSprELEbHTtkmks5tXlFigaJpZM4SQZkL.

josephsl commented 6 years ago

Hi, uh oh, @LeonardDer… Okay, please report back after you use NVDA without a braille display for a day (complete with switching back and forth between normal configuration and FF profile) and see if you can reproduce this. If it does turn out to be an issue while using a specific display, then we need to test if folks using other display models can reproduce this problem. Thanks.

From: sjtaylor82 [mailto:notifications@github.com] Sent: Thursday, February 22, 2018 9:51 PM To: nvaccess/nvda nvda@noreply.github.com Cc: Joseph Lee joseph.lee22590@gmail.com; Comment comment@noreply.github.com Subject: Re: [nvaccess/nvda] Delay of around 7 seconds when changing to application using configuration profiles other than normal (#8032)

HI Mick, Yes I do.

However, I have just changed braille input from UEB grade 2, to grade 1, and back to grade 2 again, still set to no braille.

I no longer can replicate the issue!

Come to think of it, this only started after recently using a HIMS braille display

On 23/02/2018 15:49, Michael Curran wrote:

If you Restart NVDA with add-ons disabled, do you still experience the delay?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8032#issuecomment-367916632, or mute the thread https://github.com/notifications/unsubscribe-auth/AYxk8iHv8i02QqXkekIxSprELEbHTtkmks5tXlFigaJpZM4SQZkL.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8032#issuecomment-367916863 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkBAhzoiWtxVnBDYOck2k1s79uvlhks5tXlG6gaJpZM4SQZkL .

michaelDCurran commented 6 years ago

No doubt NVDA was still configured to load the Hims driver. but as it was not connected or in range, it was falling back to No Braille.

I think I should be able to reproduce this situation with another braille display connected by bluetooth and out of range.

Thanks for reporting the issue.

michaelDCurran commented 6 years ago

Technical: I think the issue is that when Braille handles a config switch, it compares the configured display name (in this case Hims) with the currently loaded display name (in this case No Braille). As they don't match, then Braille thinks it needs to reload the display. In some cases (such as a bluetooth device being out of range) this could take a significant delay to  search and fail. We need to somehow track that No Braille was loaded due to another failed device.

josephsl commented 6 years ago

CC @DKager, @JCSTeh

LeonarddeR commented 6 years ago

After discussing this with Mick, it has been decided not to fix this in 2018.1. This is not an issue caused by the new Hims driver, however it might be the case that the new driver, due to the native way of interfacing with bluetooth devices, makes this issue more prevalent than it was before.

It will be fixed as part of braille display auto detection (#1271, #7741).