The event loop doesn't get initialized properly until first time
processEvents() is called. An in-process control that links Qt
statically constructs its own QApplication instance, but nothing
calls processEvents() on it to kickstart event processing, so
the control is unresponsive until something else causes that.

Fixed by explicitly calling processEvents() once after QApplication
instance is created.

Task-number: QTBUG-28716
Change-Id: Id50054082c75d9dce2fb12f0d44fa36601a8fc39
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>