Fix inadvertly renamed QT_THREAD_SUPPORT

Signed-off-by: Slávek Banko <slavek.banko@axis.cz>

kooka/ksaneocr.cpp

@@ -631,7 +631,7 @@ void KSANEOCR::startOCRProcess( void )
 	   // rep.Recognize();
 	   m_rep.run();
 
-	   /* Dealing with threads or no threads (using TQT_THREAD_SUPPORT to distinguish)
+	   /* Dealing with threads or no threads (using QT_THREAD_SUPPORT to distinguish)
 	    * If threads are here, the recognition task is started in its own thread. The gui thread
 	    * needs to wait until the recognition thread is finished. Therefore, a timer is fired once
 	    * that calls slotKadmosResult and checks if the recognition task is finished. If it is not,
@@ -647,7 +647,7 @@ void KSANEOCR::startOCRProcess( void )
 	    * It does not :( That is why it is not used here. Maybe some day...
 	    */
        }
-#ifdef TQT_THREAD_SUPPORT
+#ifdef QT_THREAD_SUPPORT
        /* start a timer and wait until it fires. */
        TQTimer::singleShot( 500, this, TQT_SLOT( slotKadmosResult() ));
 #else
@@ -660,7 +660,7 @@ void KSANEOCR::startOCRProcess( void )
 
 /*
  * This method is called to check if the kadmos process was already finished, if
- * thread support is enabled (check for preprocessor variable TQT_THREAD_SUPPORT)
+ * thread support is enabled (check for preprocessor variable QT_THREAD_SUPPORT)
  * The problem is that the kadmos library seems not to be thread stable so thread
  * support should not be enabled by default. In case threads are enabled, this slot
  * checks if the KADMOS engine is finished already and if not it fires a timer.