The scanning thread now generates tk events at the end of the task to signal it's completion.
Then the main thread should join() and terminate the child thread.
This is a known bad practice according to the tkinter documentation, and the side effect described in the documentation is what we are experiencing.
The scanning thread now generates tk events at the end of the task to signal it's completion. Then the main thread should join() and terminate the child thread.
This is a known bad practice according to the tkinter documentation, and the side effect described in the documentation is what we are experiencing.