CompuServe Archive

Hi John, I think it is a problem with Windows not painting the deleted edit control's rectangle correctly. To workaround this problem, you might want to explicitly invalidate the region slightly larger than that occupied by the edit control. You can do this by calling InvalidateRect() on the parent window.…

Hi Paul, >Actually, I had the controls pass the keydown/keyup and char up >to its parent. This explains why you are getting WM_KEYUP and WM_KEYDOWN but no WM_CHAR messages. Not all controls get all the messages. e.g. Buttons get key up/down messages but no WM_CHARs. What messages a control gets…

Hi Ron, The reason why you get an error in debug version and not release version is because the ASSERT macro is defined only under debug build (when _DEBUG is defined). So the problem that you are getting under debug build probably also existed under release build but the assertion…

Paul, You said that you were spying on your formview window and you were getting WM_KEYDOWN/UP messages but not WM_CHAR. Typically, you would not get those messages also in a formview. This is because if a formview has any controls, the focus would be with one of those controls and…