Freeze when launching NVDA dialogs

[nvaccessAuto]

Reported by aleksey_s on 2008-04-11 08:04
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.

[nvaccessAuto]

Comment 1 by mdcurran (in reply to comment description) on 2008-04-12 12:24
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.

[nvaccessAuto]

Comment 2 by pvagner on 2008-04-12 15:19
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.

[nvaccessAuto]

Comment 3 by jteh on 2008-04-14 02:59
As Mick noted, this ticket covers two unrelated issues. I am modifying this ticket to cover only the lag in the NVDA dialogs.
Changes:
Changed title from "improving nvda reaction in mozilla and standart dialogs" to "Freeze when launching NVDA dialogs"

[nvaccessAuto]

Comment 4 by jteh (in reply to comment 2) on 2008-04-14 03:10
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.

[nvaccessAuto]

Comment 5 by pvagner (in reply to comment 4) on 2008-04-14 04:23
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.

[nvaccessAuto]

Comment 6 by jteh on 2008-05-07 09:11
Fixed in r2023, at least on Mick's system. Please test and reopen if necessary.
Changes:
State: closed