wxWidgets Discussion Forum

I assume you tried SetForegroundColour and it didn't work? In that case, you'll probably have to use a text-less wxCheckBox plus an additional wxStaticText (hopefully you can change its text color). Great Idea! SetForegroundColour does change the color of of the wxCheckBox text, but only for the &q...

I have a wxcheckbox on a wxpanel.

I want the color of wxcheckbox text to look different in the disabled state.
How ?

Thanks, I see it now.

I just looked at the function signature, "wxThreadWait waitMode = wxTHREAD_WAIT_BLOCK" so thought that its using block mode.
But looks like I need to specify it, on MSW

@DenDev

Yes, you are right.
I was actually calling Wait, after already calling Delete, which was causing the error dialog.

While working with threads and wxThread::Delete I came across a strange behaviour. That is, if you call Delete in some event handler, while that handler has not yet finished, other events are getting processed. void MyClass::OnEvent() { print 1; m_thread->Delete(); print 2; } void MyClass::OnAnother...

I am wondering how reliable "IsRunning" is Going by your snippet ... bool YourClass::IsBusy() { if(GetThread() && GetThread()->IsRunning()) { return true; } return false; } By the time you are inside the "if block" the thread might have finished running, and you might sti...

1) You should not call the Wait() function if the thread has already been released. Before you call the Wait() function you must check that the wait operation is valid or you might get into trouble. Incase of JOINABLE threads inside wxThreadHelper "its released" only in wxThreadHelper des...

Okay, found the answer here https://forums.wxwidgets.org/viewtopic.php?t=18325 unsigned char* jpegData; // JPEG data buffer size_t jpegLen; // Length in bytes/chars of the JPEG data buffer wxMemoryInputStream jpegStream(jpegData, jpegLlen); wxImage jpegImage; jpegImage.LoadFile(jpegStream, wxBITMAP_...

@evstevemd @doublemax No, I am not trying to spawn multiple threads at the same time. A new thread is started only after the previous one has finished running. So in that context, should the previous wxThread object be used ? Call Run() again. or CreateThread be called again to create a new wxThread...

If you call the Wait() function for a thread that has already finished it will cause problems The why does the docs say (http://docs.wxwidgets.org/trunk/classwx_thread.html) Regardless of whether it has terminated or not, you should call Wait() on a joinable thread to release its memory, as outline...

I have url of an image
I download it using Curl

I have the data in a char * and a std::string

Now how to construct a wxImage using that data ?
I want to avoid saving it to a file.

wxThread::Wait frees the resources of a joinable thread.

But what about the wxThread object that the wxThreadHelper class is holding.
When I call CreateThread again, what happens to the previous wxThread object ?

evstevemd wrote:Any reasona you are not using Detached Threads?

Never thought about it. What are the pros and cons ?
There are situations when i need to manually stop threads, how would I do that with a Detached thread ?

Is it wrong to called Wait on joinable thread inside wxThreadHelper that has ended. GetThread()->Wait(); Doing so give this nice error dialog http://s3.postimg.org/3lzftrtub/wait_on_stopped_thread.png But the docs of wxThread say - Regardless of whether it has terminated or not, you should call Wait...

This is from the wxThreadHelper docs void MyFrame::DoStartALongTask() { if (CreateThread(wxTHREAD_JOINABLE) != wxTHREAD_NO_ERROR) { wxLogError("Could not create the worker thread!"); return; } if (GetThread()->Run() != wxTHREAD_NO_ERROR) { wxLogError("Could not run the worker thread!&...