Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.0.0 RC 2
-
None
-
Windows 7
-
08e38c1348639bebea7b7288a40701e4dc8d101a
Description
If Qt is built statically and an application uses an ActiveQt server via QAxWidget, both ActiveQt server and the client application have their own QApplication. However, the event loop in the QApplication of ActiveQt server is not started properly, so the control is unresponsive to mouse and keyboard until something calls processEvents the first time.
The fix seems to be calling processEvents explicitly after the QApplication has been created in CreateInstanceHelper() in qaxserverbase.cpp.