Article View: comp.os.os2.programmer
Article #2755Re: Dialogs + Threads = Problems. Help!
From: Dave Briccetti
Date: Sun, 03 Jan 1993 05:49
Date: Sun, 03 Jan 1993 05:49
25 lines
1502 bytes
1502 bytes
U37127@uicvm.uic.edu () writes: : I have received E-mail (rob@cc.gatech.edu) saying that the thread : issuing the WinSendMsg must have a msg Q as well; I also received : another answer saying that a thread *cannot* use WinSendMsg : to a window belonging to another thread (lhoang@orion.uci.edu) and : that this behaviour is documented. Apparently IBM recommends : WinPostMsg. Perhaps to maintain serialization via the msg Q : as opposed to WinSendMsg which is a direct call to the function? : : Is there a definitve doc anywhere on this subject? My interim kludge has been : to use WinPostMsg, with an app defined msg, and block until the receiver : processes the msg and shoves the result into a shared data structure. The notes in the PM Reference make it quite clear that WinSendMsg to a window belonging to another thread IS allowed. The message is sent synchronously and the thread switching is automatic. I've done it myself for years. -- Dave Briccetti, Owner, Dave Briccetti & Associates OS/2 Developer/Consultant P.O. Box 1713 Lafayette, CA 94549-7013
Technical Details
Message-ID:
<1993Jan3.054918.1861@netcom.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!spool.mu.edu!umn.edu!csus.edu!netcom.com!davebReferences:
<92366.110046U37127@uicvm.uic.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!spool.mu.edu!umn.edu!csus.edu!netcom.com!daveb From: daveb@netcom.com (Dave Briccetti) Subject: Re: Dialogs + Threads = Problems. Help! Message-ID: <1993Jan3.054918.1861@netcom.com> Organization: Dave Briccetti & Assoc., OS/2 Consulting References: <92366.110046U37127@uicvm.uic.edu> Date: Sun, 3 Jan 1993 05:49:18 GMT Lines: 25