Re: why UI gets hangs

I think this may be the biggest confusion. I know I still get caught by
this at times. It is so easy to put in something like AfxMessageBox() into
the worker thread and that just gets me (and I assume others) into trouble.
It works sometimes, but... I've also been caught when I tried to do that
sort of thing (UI) from a callback from a DLL function (like a message
server listener) which may (even though I don't know it) be running on its
own thread. My personal opinion these days is when in doubt send a message
to the UI thread. I also never call functions direction in dialogs or views
(except through UpdateAllViews()). This is a tough thing to get used to
since it's so easy to just grab a view pointer and call a function in the
class to update some text or whatever, but over all it really cleans the
code up when you just don't do this sort of thing and, instead, send a
message. I've found that that messages typically get processed immediately
if the bandwidth is clear so the net effect on the user's experience is the
same, but the program runs much better and more reliably. Nothing like
popping up an AfxMessageBox() with no text in it because the DLL thread has
it's own resources :o)

I know you agree, I'm just adding comments to the thread (forum thread that
is, not the worker thread) :o)

Tom

"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:BZREj.1446$p24.306@nlpi061.nbdc.sbc.com...