Windows (tested on XP Pro SP2) is sending this message to my app at
semi-random intervals, and the message gets passed to DefWindowProc.
DefWindowProc then apparently paints the nonclient area of the window using
the default nonclient-area-drawing code --- which is exactly the wrong
behavior, because I've overriden *all* of the documented WM_NC* messages in
my window procedure. The result is that at (nearly) unpredictable intervals,
the window suddenly gets ugly gray lines all over it.
In my code, I've simply added a line to test for the 0xAE message and just
return 0. This seems to work fine, but I wonder if it has other side-effects.
So does anybody know anything at all about what this message is? I'd really
appreciate knowing so I can determine what to do next.
--
Do you suppose if I put a signature here anyone would bother to read it?
No? I didn't think so either.