>>Nick,
>>
>>I know we all call it a "wait state" (what read events results in), but I must admit that when I read that "explanation" I found myself wondering why they didn't call it "Wait Events" since what it really does ia let us "wait" for a user to *do* something (causing an event).
>>
>>My *guess* would be that "wait state" is the "easy out" for an explanation, and that more likely something much more fundamental is actually going on. Something along the lines of giving WIN "control" on our behalf, at the same time identifying our app as the "owner" of specific rel-estate on the screen.
>>
>>Not diagreeing with you, just adding commentary.
>>Cheers
>>Jim N
>>
>Jim, I agree that something is going on behind the scenes, MS just forgot to tell us what. :) BTW, WAIT EVENTS is a great name for that.
>
>Nick
Nick,

So then just;

#DEFINE WAIT_EVENTS READ EVENTS


Do stuff

WAIT_EVENTS