From 2b2681187163fd487a6033e10b0f8e002d698318 Mon Sep 17 00:00:00 2001
From: Manuel Schneider
Date: Fri, 25 Apr 2014 13:07:50 +0200
Subject: Now using qWidget instead of qDialog to avoid the need to handdle
 every dialog event (reject, done, accept, finished). No more close override
 necessary.

---
 src/client/vnc/vncthread.cpp | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'src/client/vnc/vncthread.cpp')

diff --git a/src/client/vnc/vncthread.cpp b/src/client/vnc/vncthread.cpp
index fe52283..7d23afa 100644
--- a/src/client/vnc/vncthread.cpp
+++ b/src/client/vnc/vncthread.cpp
@@ -118,14 +118,14 @@ void VncThread::setTargetSize(const QSize size)
 }
 
 /**
- * Worker thread's mainloop, connecting to the VNC server and handling the connection.
- * The vnc client library is written in a blocking manner, so we just do everything in
- * our own thread and just hand over the image updates to the vnc client window, which
- * resides in the application's main thread.
+ * Worker thread's mainloop, connecting to the VNC server and handling the
+ * connection.  The vnc client library is written in a blocking manner, so we
+ * just do everything in our own thread and just hand over the image updates to
+ * the vnc client window, which resides in the application's main thread.
  *
- * This thread checks if the vnc window signaled us to stop and if so, it deletes itself.
- * This means that you should *never* delete this thread from anywhere. Just call VncThread::stop()
- * and wait for it to delete itself.
+ * This thread checks if the vnc window signaled us to stop and if so, it
+ * deletes itself.  This means that you should *never* delete this thread from
+ * anywhere. Just call VncThread::stop() and wait for it to delete itself.
  */
 void VncThread::run()
 {
-- 
cgit v1.2.3-55-g7522