EDN Admin
Well-known member
Hello!
Ive noticed an irritating behaviour of the Windows Magnifier and a standard single document MFC application generated by the new project wizard of VC++ 8.0 with enabled support for Active Accessibility and even <span class=moz-txt-star><span class=moz-txt-tag>without<span class=moz-txt-tag> enabled Active Accessibility when using a CFormView based view.
As soon as the Windows Magnifier (magnify.exe) is running, an accessible proxy is created through CWnd::CreateAccessibleProxy. The creation of a CMFCComObject increases the OLE lock count by calling AfxOleLockApp.
However, this lock count is not decreased any more. As a consequence, the call to AfxOleCanExitApp in CFrameWnd:: OnClose returns false and prevents the application from closing correctly. Finally, a ghost process is listed in task manager.
Is this a bug in MFC or in Windows Magnifier? Can anyone please point me to a possible solution to this problem?
Thanks!
Kind regards,
Florian Heidenreich
View the full article
Ive noticed an irritating behaviour of the Windows Magnifier and a standard single document MFC application generated by the new project wizard of VC++ 8.0 with enabled support for Active Accessibility and even <span class=moz-txt-star><span class=moz-txt-tag>without<span class=moz-txt-tag> enabled Active Accessibility when using a CFormView based view.
As soon as the Windows Magnifier (magnify.exe) is running, an accessible proxy is created through CWnd::CreateAccessibleProxy. The creation of a CMFCComObject increases the OLE lock count by calling AfxOleLockApp.
However, this lock count is not decreased any more. As a consequence, the call to AfxOleCanExitApp in CFrameWnd:: OnClose returns false and prevents the application from closing correctly. Finally, a ghost process is listed in task manager.
Is this a bug in MFC or in Windows Magnifier? Can anyone please point me to a possible solution to this problem?
Thanks!
Kind regards,
Florian Heidenreich
View the full article