Critical Section for one thread

[Force Code]

How would you implement a critical section between two or more windows in a single thread, i.e. if one winproc tries to access it, it halts in place till its available, while other windows in thread continue to function and continue to recieve messages. I know CriticalSections work for threads, not windows - I was thinking of something implemented with GetMessage, PeekMessage or whatever. Maybe this is impossible.

[Mark Salsbery]

If you only have one thread there's no way to halt that thread and have anything else happen in your windows or window proc(s) (aside from asynchronous callbacks, of course, but those are separate threads). With a single thread, while a windowproc is handling a message, all other window procs are halted. Mark

Mark Salsbery Microsoft MVP - Visual C++ :java:

[Force Code]

Mark Salsbery wrote:

If you only have one thread there's no way to halt that thread and have anything else happen in your windows or window proc(s) (aside from asynchronous callbacks, of course, but those are separate threads). With a single thread, while a windowproc is handling a message, all other window procs are halted.

Well, if a resource is unavailable, why couldn't a WinProc start a GetMessage-Translate-Dispatch loop right there until a special message was sent indicating the resource was available, at which point the WinProc would halt the GetMessage Loop and continue as normal. I'm not understanding why this doesn't work.

[Mark Salsbery]

Because that "GetMessage-Translate-Dispatch loop" is running on the same thread you start it on.  Everything occurs serially until there's another thread. Mark

Mark Salsbery Microsoft MVP - Visual C++ :java: