![]() I think it makes it very unstable and then with in the next second or so it will crash (as I do sometimes get to see the start of the progress dialog, and usually 1 or two beeps). However the call to accParent doesn't seem to crash the app via the call atomically. This text node very quicly gets focus as you close the first dialog (before the second progress dialog gains focus). I have narrowed the issue down to a call to IAccessible::get_accParent on an Acrobat text node IAccessible (the one that says alert document being processed). However, I think it happens for me whether or not the navigation pane is there or not. I can definitely reproduce the crash with an untagged document. NOTE: Before I upgraded to Adobe Reader 10, I was using Adobe Reader 9.4.1 also with the latest snapshots of NVDA and didn't experience such problems. But if you manage to press F4 immediately after opening the PDF from the 1st link and by doing that closing (hiding) the "Navigation pane", it is more likely that Adobe Reader will not crash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |