Re: Closing modeless dialogs

Thanks everyone for the numerous answers. Now I see that my "workaround"
is a bad idea, a hack indeed.

I changed my application and I'm now using a worker thread. Instead of
using a modeless dialog I'm using a modal dialog (but I disabled closing
the dialog manually). In OnInitDialog I create a new thread that
performs the actual operation.

I added a function CloseDialog to my dialog to close the dialog.
CloseDialog calls CDialog::EndDialog - is this a good idea?

During the operation I need to update the text displayed in the dialog.
My naive approach is that the worker thread can access the dialog object
and calls a function called SetText that will call SetWindowText and
UpdateWindow - I suppose that this is no good idea, I should use
messages instead, is that right? If yes - why? I will only access the
dialog from the worker thread and never from anywhere else.

In a different application (where I didn't code the threading issues) we
had several problems with messages: the dialog was dismissed, but some
messages weren't processed yet, or messages were processed, but the
pointer to the message content (a char*) was not valid anymore since the
CString the char* pointed to was deleted.