WinRT: move most of GUI event dispatcher logic into core

The native event dispatcher is responsible for delivering callbacks
to non-GUI handlers, such as network socket listeners. So, the non-GUI
logic is moved into the core dispatcher so that the event loop works
better for apps (and test cases) which use QCoreApplication.

Change-Id: Ic5f7d939cf164198fd39aa5880e265ae560b39b4
Reviewed-by: Oliver Wolff <oliver.wolff@digia.com>

1 files changed, 2 insertions, 21 deletions

diff --git a/src/plugins/platforms/winrt/qwinrteventdispatcher.h b/src/plugins/platforms/winrt/qwinrteventdispatcher.h
index 741007c7fa..612d5ff6e2 100644
--- a/src/plugins/platforms/winrt/qwinrteventdispatcher.h
+++ b/src/plugins/platforms/winrt/qwinrteventdispatcher.h
@@ -44,36 +44,17 @@
 
 #include <QtCore/private/qeventdispatcher_winrt_p.h>
 
-#include <wrl.h>
-
-namespace ABI {
-    namespace Windows {
-        namespace UI {
-            namespace Core {
-                struct ICoreDispatcher;
-            }
-        }
-    }
-}
-
 QT_BEGIN_NAMESPACE
 
 class QWinRTEventDispatcher : public QEventDispatcherWinRT
 {
     Q_OBJECT
 public:
-    explicit QWinRTEventDispatcher(ABI::Windows::UI::Core::ICoreDispatcher *dispatcher, QObject *parent = 0);
+    explicit QWinRTEventDispatcher(QObject *parent = 0);
 
 protected:
-    void interrupt();
     bool hasPendingEvents();
-    bool processEvents(QEventLoop::ProcessEventsFlags flags);
-
-private:
-    Microsoft::WRL::ComPtr<ABI::Windows::UI::Core::ICoreDispatcher> m_dispatcher;
-    bool m_interrupt;
-
-    friend class QWinRTIntegration;
+    bool sendPostedEvents(QEventLoop::ProcessEventsFlags flags);
 };
 
 QT_END_NAMESPACE