Ticket #65 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Freeze when launching NVDA dialogs

Reported by: aleksey_s Owned by:
Priority: major Milestone: 2009.1
Component: GUI Version: development
Keywords: Cc:
Operating system: Blocked by:
Blocking:

Description (last modified by jteh) (diff)

When an NVDA dialog is launched from a script (e.g. NVDA+Q for Exit NVDA dialog, NVDA+Control+F for find dialog, NVDA+Control+S for Synthesizer dialog), on some systems, NVDA frequently stops responding for at least a second. After this time has elapsed, operation resumes normally.

Change History

in reply to: ↑ description   Changed 2 years ago by mdcurran

I would say that this should be two separate tickets. These problems are definitely not related. Keeping this ticket as the problem with the synthesizer dialog, it can be also said that this is related to the 1-second pauses I get occasionally for the NVDA exit dialog and the NVDA find dialog. Note that for me at least, the synthesizer dialog only pauses if called with nvda+control+s, but not from with in the NVDA menu.

follow-up: ↓ 4   Changed 2 years ago by pvagner

Guys I haven't noticed problems in the mozilla dialogs so far but I am afraid there might really be a serious issue with NVDA dialogs. It's mainly noticeable with find dialog and error dialog. Also sythesizer and voice settings dialog seem to be affected. When the dialog is inwoked it is correctly reported but interacting with the control in focus is not possible. I do need to focus away and return back in order to interact with the control which was focused originally.

  Changed 2 years ago by jteh

  • priority changed from critical to major
  • component changed from Core to GUI
  • description modified (diff)
  • summary changed from improving nvda reaction in mozilla and standart dialogs to Freeze when launching NVDA dialogs

As Mick noted, this ticket covers two unrelated issues. I am modifying this ticket to cover only the lag in the NVDA dialogs.

in reply to: ↑ 2 ; follow-up: ↓ 5   Changed 2 years ago by jteh

Replying to pvagner:

I am afraid there might really be a serious issue with NVDA dialogs. ... When the dialog is inwoked it is correctly reported but interacting with the control in focus is not possible. I do need to focus away and return back in order to interact with the control which was focused originally.

I suspect this is yet again another issue. It sounds like the NVDA dialogs aren't receiving focus correctly on your system, similar to the issues with the old GUI described in #28. NVDA does receive the focus event, but the window does not become the foreground window, so it hasn't really received focus, even though NVDA thinks it has. You can test this by pressing alt+space and then alt to open the system menu. When you exit the menu, NVDA will find the correct focus. If this is the case for you, we either need to reopen #28 or create a new ticket for focus issues in the new GUI.

in reply to: ↑ 4   Changed 2 years ago by pvagner

Replying to jteh:

I suspect this is yet again another issue. It sounds like the NVDA dialogs aren't receiving focus correctly on your system, similar to the issues with the old GUI described in #28. NVDA does receive the focus event, but the window does not become the foreground window, so it hasn't really received focus, even though NVDA thinks it has. You can test this by pressing alt+space and then alt to open the system menu. When you exit the menu, NVDA will find the correct focus. If this is the case for you, we either need to reopen #28 or create a new ticket for focus issues in the new GUI.

Now I have tested it again and I gave it a bit of time.
The controls are focused right it just takes a little bit longer to make them usable. E.G. when opening voice settings dialog I can hear voice settings dialog and I expect I am able to press ctrl or up/down arrow and move in the list but I do need to wait half a second or so until that's finally possible.
With settings dialog this is not such an issue because they are not opened frequently but it really anoys me while using search dialog with the new virtual buffers.

  Changed 22 months ago by jteh

  • status changed from new to closed
  • resolution set to fixed

Fixed in r2023, at least on Mick's system. Please test and reopen if necessary.

Note: See TracTickets for help on using tickets.