Actually it was a mistake, thanks for sending it! I was starting to
wonder where the blazes it went!
Yes that restriction might be a bit of an issue, however I *suppose*
information on the control (not the control itself) could be serialized
and sent over a Queue to the process altering the control. I have yet to
test this. Be Careful.
A few months back I hinted at some code that Rob had built that would make
threading coding much easier for Win32-GUI apps. In light of your recent
examples, I've dropped him an offlist mail suggesting that his code be
available to more people. Although not complete, it is a great platform to
build from.
One of the problems that Rob's code solves is that one end of a thread
message queue can be attached to a window meaning there are no sleeps or
polling to check for new messages. Basically, it means that a working thread
can fire events in the thread controlling the window, resulting in a very
efficient and simple event driven threading model.
Cheers,
jez.
