eeva/jamulus
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

lowering the GUI thread priority should not be necessary if the high priority socket thread is correctly implemented

Browse source
This commit is contained in:
Volker Fischer 2014-01-31 16:51:06 +00:00
parent ab8fbae16d
commit 76d8de72b6
1 changed files with 0 additions and 8 deletions

8
src/main.cpp
View file

@ -375,14 +375,6 @@ int main ( int argc, char** argv )
// set application priority class -> high priority // set application priority class -> high priority
SetPriorityClass ( GetCurrentProcess(), HIGH_PRIORITY_CLASS ); 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 // 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. // be located in the install directory of the software by the installer.
// Here, we set the path to our application path. // Here, we set the path to our application path.