From 76d8de72b688390fa4b4fc63efc97bed8d0de7d8 Mon Sep 17 00:00:00 2001 From: Volker Fischer Date: Fri, 31 Jan 2014 16:51:06 +0000 Subject: [PATCH] lowering the GUI thread priority should not be necessary if the high priority socket thread is correctly implemented --- src/main.cpp | 8 -------- 1 file changed, 8 deletions(-) diff --git a/src/main.cpp b/src/main.cpp index 97c866c8..e1bf5d55 100755 --- a/src/main.cpp +++ b/src/main.cpp @@ -375,14 +375,6 @@ int main ( int argc, char** argv ) // set application priority class -> high priority SetPriorityClass ( GetCurrentProcess(), HIGH_PRIORITY_CLASS ); -#ifdef ENABLE_RECEIVE_SOCKET_IN_SEPARATE_THREAD - // Since we have a higher priority for the entire application, we can give - // the GUI thread the lowest possible priority which is still above the - // Windows "normal" priority so that it does not slow down the sound card - // and network working threads. - QThread::currentThread()->setPriority ( QThread::LowestPriority ); -#endif - // For accessible support we need to add a plugin to qt. The plugin has to // be located in the install directory of the software by the installer. // Here, we set the path to our application path.