-=> Quoting Peter Fitzsimmons to Joachim Jaeckel <=- 


 PF> 1) During WM_INITDLG, the dialog has not been completely created
 PF> yet.  If your thread starts accessing stuff before its ready,
 PF> problems might occur.

 PF> 2) Any thread that accesses PM must call WinInitialize().

Petzold mentions that it is a good habit to always call
WinInitialize(0) for -all- threads that are created, but he never says
why?  I guess this is why! :-)

 PF> 2b) Any thread that accesses many (if not most) Win/Gpi calls
 PF> must create a message queue (WinCreateMsgQueue).

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

--- Blue Wave/OS2 v2.30