Re: Your advice about WorkerThreads vs UI Threads

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 2 Apr 2007 10:39:08 -0700

Message-ID:

<0BB6AAE7-615B-46C1-BB04-5EECD9B64BC8@microsoft.com>

I use worker threads and just have them send messages to the UI if something
needs to be updated or a dialog needs to be displayed, etc. I like only
having one UI thread.

Tom

"MrAsm" <mrasm@usa.com> wrote in message
news:btc2139ct0v1oi9puflv24r5t7u6ochshh@4ax.com...

Hi,

I would like to do a computation and don't want the GUI to look "dead"
during this computation.
So, I was thinking about worker threads - the computation is done by
worker thread.

So I was studying Joe's essay about worker threads:

http://www.flounder.com/workerthreads.htm

But I also read on his web site about User Interface threads, and I
read that UI threads don't necessarily have user-interface objects:

http://www.flounder.com/uithreads.htm

So I was wondering if, for doing long computations, it is better to
start a Worker thread or a UI thread.
I was thinking about worker thread (also because I thought -
uncorrectly - that UI threads must have user-interface objects), but
Joe's essay about worker threads clearly show that there are several
non-trivial issues to consider with worker thread, on the other side
it seems that the essay about UI threads is simpler.

Thanks for your advice,
MrAsm