Article View: comp.os.os2.programmer
Article #3261Re: Dialogs + Threads = Problems. Help!
From: Dennis.Ingram
Date: Mon, 04 Jan 1993 20:58
Date: Mon, 04 Jan 1993 20:58
21 lines
1314 bytes
1314 bytes
> 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 As I understand it, in order for a thread to use WinSendMsg it must have a message queue. I have always wondered what is the best thing to do when you have multiple threads that need to access a window - do you use WinPostMsg and block using semaphores, or define a queue and use WinSendMsg? What is the overhead of defining a message queue (in terms of system resources), bearing in mind that the queue is only there to allow WinSendMsg access?
Technical Details
Message-ID:
<1993Jan4.205811.107@actrix.gen.nz>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!actrix!Dennis.IngramReferences:
<92366.110046U37127@uicvm.uic.edu> <1993Jan3.054918.1861@netcom.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!actrix!Dennis.Ingram From: Dennis.Ingram@bbs.actrix.gen.nz Subject: Re: Dialogs + Threads = Problems. Help! Organization: Actrix Information Exchange Date: Mon, 4 Jan 1993 20:58:11 GMT Message-ID: <1993Jan4.205811.107@actrix.gen.nz> References: <92366.110046U37127@uicvm.uic.edu> <1993Jan3.054918.1861@netcom.com> Sender: Dennis.Ingram@actrix.gen.nz (Dennis Ingram) Lines: 22