WTL eats up the messages
-
Example one: I create custom (dialog based) toolbar. CMainFrame winproc eats up RBN_AUTOSIZE, so my view has resizing problems. Temp Fix NOTIFY_CODE_HANDLER(RBN_AUTOSIZE, ...) at the beginning of the message map. Example two: on a property page (CPropertyPageImpl) I try to create owner drown combo. CPropertyPageImpl winproc eats up WM_DRAWITEM for the edit part. Fix is similar to intercept WM_DRAWITEM and ::SendMessage(((LPDRAWITEMSTRUCT)lParam)->hwndItem .... There is obviously something that I am doing wrong in my code that makes WTL/ATL winprocs to eat up the messages. Any ideas?
-
Example one: I create custom (dialog based) toolbar. CMainFrame winproc eats up RBN_AUTOSIZE, so my view has resizing problems. Temp Fix NOTIFY_CODE_HANDLER(RBN_AUTOSIZE, ...) at the beginning of the message map. Example two: on a property page (CPropertyPageImpl) I try to create owner drown combo. CPropertyPageImpl winproc eats up WM_DRAWITEM for the edit part. Fix is similar to intercept WM_DRAWITEM and ::SendMessage(((LPDRAWITEMSTRUCT)lParam)->hwndItem .... There is obviously something that I am doing wrong in my code that makes WTL/ATL winprocs to eat up the messages. Any ideas?
Perhaps adding the REFLECT_NOTIFICATIONS() macro to the message map would be helpful.
-
Perhaps adding the REFLECT_NOTIFICATIONS() macro to the message map would be helpful.