If one uses a log window, as implemented at https://github.com/chwba/concur_gui_test/blob/847d94a4d85271131023d2435a9c23d1698e6e39/src/features/base/BaseGUI.py#L109 and prints a lot of messages very fast, the log will get very slow, so slow that it cannot follow the actual execution speed anymore. Can be easily reproduced by cloning the above mentioned repo, printing like 2.000 messages in a for loop and then returning from the function printing them, it will cause that not all messages are being printed because the process/thread terminates before the queue is empty.
In my case I had to add while Trues, which keep checking for if the loq queue is now empty to make sure all messages will even be printed before the app terminates.
If one uses a log window, as implemented at https://github.com/chwba/concur_gui_test/blob/847d94a4d85271131023d2435a9c23d1698e6e39/src/features/base/BaseGUI.py#L109 and prints a lot of messages very fast, the log will get very slow, so slow that it cannot follow the actual execution speed anymore. Can be easily reproduced by cloning the above mentioned repo, printing like 2.000 messages in a for loop and then returning from the function printing them, it will cause that not all messages are being printed because the process/thread terminates before the queue is empty.
In my case I had to add while Trues, which keep checking for if the loq queue is now empty to make sure all messages will even be printed before the app terminates.
Any idea how we could accelerate this procedure?