-=> Quoting Eelco Dolstra to Phil Crown <=- 

 PC> If I use a wrapper for WinPostMsg such as below, doesn't this 
 PC> defeat the purpose of WinPostMsg's attribute of returning without

 ED> Yes, but this would only happen if the receiver's message queue is
 ED> full and remains full, which doesn't (or shouldn't) happen very often.
 ED> Then PostMsg would indeed violate the 1/10th second rule. A solution
 ED> might be to put a time-out or a counter in PostMsg, so that it would
 ED> return after some time. 
 ED> Eelco.

Thanks for the reply.

I have another question perhaps you or somebody can help me with.

I have a main thread and a background thread each with its own message queue
created by WinCreateMsgQueue().

The background thread is a child of HWND_OBJECT so it doesn't have to
respond to the normal messages as it would if it were a visible window.

I post messages to the background thread when I want to do some time
consuming task that would otherwise block the main thread's message queue
for an unacceptable lenght of time.

However, this may block the Object windows queue for quite sometime.

Do I not have to worry about blocking an Object windows queue as I do the
main thread's queue?

Or should I have the Object Window Procedure start another thread to do time
consuming tasks?

Phil
Fido:  1:124/8014.1 | Internet:  phil.crown{at}bluecafe.com


--- Blue Wave/Max v2.22b