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, 3 insertions, 2 deletions

diff --git a/client/screen.cpp b/client/screen.cpp
index b33560ee..5d138a1c 100644
--- a/client/screen.cpp
+++ b/client/screen.cpp
@@ -30,9 +30,10 @@ class UpdateEvent: public Event {
 public:
     UpdateEvent(int screen) : _screen (screen) {}
 
-    virtual void responce(Application& application)
+    virtual void response(AbstractProcessLoop& events_loop)
     {
-        RedScreen* screen = application.find_screen(_screen);
+        Application* app = static_cast<Application*>(events_loop.get_owner());
+        RedScreen* screen = app->find_screen(_screen);
         if (screen) {
             screen->update();
         }