Problem Exporting Beast To wxWidgets
-
- Earned some good credits
- Posts: 125
- Joined: Wed Oct 28, 2015 9:48 pm
Re: Problem Exporting Beast To wxWidgets
Thank you so much for helping me. It is working now.
Re: Problem Exporting Beast To wxWidgets
Just for the information, I believe that doublemax made a typo here and the sentence should read "Beware that you're NOT allowed to use GUI elements from inside secondary threads in wxWidgets"doublemax wrote:Beware that you're allowed to use GUI elements from inside secondary threads in wxWidgets.
-
- Earned some good credits
- Posts: 125
- Joined: Wed Oct 28, 2015 9:48 pm
Re: Problem Exporting Beast To wxWidgets
Thanks to everyone for helping. I really do appreciate it.
How do I kill the thread when the main window closes. Right now I spin that thread off, then it hangs (waiting for a http response). I would like that thread to end when the window closes.
How do I kill the thread when the main window closes. Right now I spin that thread off, then it hangs (waiting for a http response). I would like that thread to end when the window closes.
-
- Super wx Problem Solver
- Posts: 466
- Joined: Tue Jun 20, 2006 6:47 pm
- Contact:
Re: Problem Exporting Beast To wxWidgets
The thread sample shows one way to do this. The approach used there is to have a bool variable in the app class indicate that the application is shutting down. The threads then check that variable periodically to see if they should terminate.Everydaydiesel wrote:Thanks to everyone for helping. I really do appreciate it.
How do I kill the thread when the main window closes. Right now I spin that thread off, then it hangs (waiting for a http response). I would like that thread to end when the window closes.
Also, a semaphore is used in the destructor for the main form to keep it from being destroyed until all threads are terminated.