Reported by ianr on 2011-05-26 17:57
When I open SSMS while NVDA is running NVDA stops speaking.
My current workaround is to get ready to open SSMS, close NVDA, then open SSMS and restart NVDA.
I will attach a log file.
Blocked by #1408
Attachment nvda.log added by ianr on 2011-05-26 17:59
Attachment without braille display nvda.log added by ianr on 2011-05-26 18:07
This log is from a fresh nvda start with my braille display detached to show that my braille display is not causing the freeze.
Comment 1 by jteh on 2011-05-26 22:15
Surprise surprise. Another freeze in isUIAWindow.
Comment 2 by jteh on 2011-05-26 22:19
Is this app free or paid? If paid, we're unfortunately not going to be able to debug this specific case.
Comment 3 by ianr on 2011-05-26 22:35
This application is free and can be downloaded at this link:
Ticket #912 also refers to this application.
Comment 4 by ianr on 2011-05-26 22:44
This differs a little from ticket 1408 as in 1408 nvda is affected because the other application is not responding. In this application the application continues to respond normally, but nvda stops responding.
If these are problems with UI Automation and you have reported them to Microsoft is there any way users can show their support for Microsoft to fix UIA? ie. a Microsoft ticket we can comment on or anything?
Comment 5 by jteh on 2011-05-26 23:02
The only reason I know of that isUIAWindow might freeze is if a window stops responding. Note that it doesn't have to be the whole application; it could just be one window. Sometimes, applications seem to create unresponsive windows and then hide them, even though they really shouldn't. I'd have to debug further to know. If this is the case, technically, it's a bug in the application, though the function should at least time out or something. Anyway, it is related to #1408, even if the symptoms seem different.
We haven't formally reported these issues to Microsoft because they're very difficult to reproduce outside of very specific circumstances (including running a screen reader) and I suspect Microsoft aren't particularly interested in testing with NVDA. Also, we've been told on other occasions that the chances of getting an accessibility related fix into an earlier version of software is highly unlikely and it would cost us money just to file the issue.
Comment 6 by jteh on 2011-09-05 10:37
Can you please confirm whether this is fixed by 7366dee? (A snapshot for this should be available in about 23 hours.)
Comment 7 by ianr on 2011-09-07 03:09
I tested with snapshot 4634 and the problem is fixed. Thanks very much!
Comment 8 by jteh on 2011-09-07 07:11
Milestone changed from None to 2011.3