This case is really prevalent there clearly was a work entitled PostQuitMessage so you can article WM_Prevent. PostMessage always works more effectively when you wish so you’re able to replicate a demand otherwise input feel from the post WM_Demand otherwise among the piano otherwise mouse messages (that is always dicey, in addition). So it holds true since “real” input situations always have been in sequences from relevant messages (like keydown/keyup pairs) and your app could get befuddled if you try to help you processes another type of enter in content in the middle of one of these sequences. Article works more effectively when simulating input. Often you must have fun with PostMessage to acquire as much as a beneficial quirk otherwise bug to prevent unlimited recursion. Like, guess your own WM_SETFOCUS handler (OnSetFocus) establishes that the new desire windows isn’t perfect for particular reasoning and you have to change the main focus to another windows.

For those who name SetFocus from the inside your OnSetFocus handler, Screen immediately directs another WM_SETFOCUS messagea€”when you are nonetheless processing the original you to!

The result is unlimited regress up until your stack blows right up. To get rid of this infelicity, you could blog post a contact to yourselfa€”MYWM_SWITCHFOCUSa€”so OnSetFocus can be end one which just process the content to alter the main focus. Continuarea →