This will be the case. I recently changed the code to not fire WM_SIZE messages if…
+ From: Michal Bukovjan
+
+ This will be the case. I recently changed the code to not fire WM_SIZE
+ messages if WM_WINDOWPOSCHANGED is handled, which is always.
+ I suggest either moving the line setting code into this message,
+ or maybe should the WM_SIZE message be fired after all?
As far as I can recall a WM_SIZE event is allways fired. I just did some experiments, WM_WINDOWPOSCHANGED is fired allways. If you don't call inherited in the WM_WINDOWPOSCHANGED handler, WM_SIZE won't get fired otherwise it will.
Looking at Delphi, it calls UpdateBounds on a WM_SIZE event and a WM_WINDOWPOSCHANGED.
I think we should do the same.
Marc