Re: The basics of Windows' messages
- From: Ney André de Mello Zunino <zunino@xxxxxxxxxxx>
- Date: Thu, 08 Jun 2006 08:39:42 -0300
adebaene@xxxxxxxxxxxxxxxx wrote:
William as already answered your questions about 2) in great details,
but I would like to add that most experienced developers consider 2) to
be a bad choice, and 1) to be the correct solution.
[...]
I have always regarded option 2) as a lazy/lousy programmer's attempt to simulate option 1). The reason I focused my question on option 2) is that I wish to understand the execution flow from the point amid the lengthy process, where /ProcessMessages/ is called, to the queue processing, and then back to the calling site, where the lengthy process is resumed. William's response has already taken me much closer in that direction, but I think I might still need another round.
Thank you and best regards,
--
Ney André de Mello Zunino
.
- References:
- The basics of Windows' messages
- From: Ney André de Mello Zunino
- Re: The basics of Windows' messages
- From: William DePalo [MVP VC++]
- Re: The basics of Windows' messages
- From: Ney André de Mello Zunino
- Re: The basics of Windows' messages
- From: adebaene
- The basics of Windows' messages
- Prev by Date: Re: ReadDirectoryChangesW
- Next by Date: Re: The basics of Windows' messages
- Previous by thread: Re: The basics of Windows' messages
- Next by thread: Re: The basics of Windows' messages
- Index(es):
Relevant Pages
|