https://issues.apache.org/ooo/show_bug.cgi?id=123640
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from V Stuart Foote <[email protected]> --- Jamie, Steve (In reply to James Teh from comment #5) > ... However, it occurred to me that the old OO build might have > broken MSAA. That seems to have been the issue! >You can fix this by registering c:\windows\system32\oleacc.dll > and c:\windows\system32\oleaut32.dll. You may need to unregister and then > register if it complains that it's already registered. I first registered oleacc.dll -- regsvr32 oleacc.dll, no complaint that it was already registered. Launch of AOO 4.1.0 ia2 r1538508 comes up clean and is being rendered by NVDA and Accprobe shows MSAA and IAccessible2 content. Then also registered oleaut32.dll -- regsvr32 oleaut32.dll, no complaint there either. A review of the system log did not show any error events from oleacc during prior sessions, but guess that makes sense if the library was not registered. Would the broken MSAA manifest in some other log? I'm fine with closing resolved--but if removal of older ia2 caused the mangled MSAA is it fixed or not-a-bug. Potentially some other beta testers will have the same experience. At least a note in the ia2 branch tips: https://cwiki.apache.org/confluence/display/OOOUSERS/Tips+for+branch+ia2 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
