spice client: creating a general process loop.

The process loop is responsible for: 1) waiting for events 2) timers 3) events queue for
actions that should be performed in the context of the thread and are pushed from other threads.
The benefits:
1) remove duplicity: till now, there was one implementaion of events loop for the channels and
another one for the main thread.
2) timers can be executed on each thread and not only on the main thread.
3) events can be pushed to each thread and not only to the main thread.
In this commit, only the main thread was modified to use the new process loop.

1 files changed, 2 insertions, 1 deletions

diff --git a/client/x11/events_loop_p.h b/client/x11/events_loop_p.h
index 0a70d3ed..d339ca4b 100644
--- a/client/x11/events_loop_p.h
+++ b/client/x11/events_loop_p.h
@@ -31,6 +31,7 @@ class EventWrapper;
 
 class EventsLoop_p {
 public:
+    class Trigger_p;
     void remove_wrapper(EventWrapper*);
 
 public:
@@ -41,7 +42,7 @@ public:
     friend class EventWrapper;
 };
 
-class Trigger_p {
+class EventsLoop_p::Trigger_p {
 public:
     Trigger_p() : _pending_int (false) {}
     int get_fd() { return _event_fd;}