Here's a weird one. I'm trying to change my app so that when a mouse
click activates a window I automatically discard the mouse click (so
that unpausing doesn't inadvertently allow the user to exit the game,
restart, etc.).
I was originally going to do this programmatically by letting my main
app look at the timestamps of the last activation message vs. incoming
mouse down events, but the delta can vary by a significant amount of
time (at least 2ms). Trying to make this work by altering the tolerance
seems iffy at best.
The next thing I decided to look at was WA_CLICKACTIVE, but while
looking at that I found WM_MOUSEACTIVATE and returning
MA_ACTIVATEANDEAT. Unfortunately, my app NEVER sees a WM_MOUSEACTIVATE
-- I've confirmed this with Spy++. This is on Win2K. However, someone
else I know sees this event just fine -- any ideas what's going on here?
Failing WM_MOUSEACTIVATE, I'll look into WA_CLICKACTIVE and set a flag
to ignore the next mouse message, but now I'm curious what's up with
WM_MOUSEACTIVATE.
Brian
|
