Capturing WM_ACTIVATE in CPropertyPage

dennisV

Hello, I have a CPropertySheet with a few property pages embedded in a form view. I would like to capture the WM_ACTIVATE message to see when I should write/read data from/to property pages. The problems is the the form view is eating up that message. I can only monitor WM_CHILDACTIVATE and OnKillActive(), but that doesn't cover all cases. I want to save data whenever a user clicks away from the property sheet. How can I do that? Any help greatly appreciated! MCP, MCSD

RaviBee

Override OnSetActive() when you want to (re)set the property page's controls. Override OnKillActive() and OnOK() (and optionally OnApply()) to capture the settings from the property page. /ravi Let's put "civil" back in "civilization" Home | Articles | Freeware | Music ravib@ravib.com

Michael Dunn

WM_ACTIVATE isn't the right message for a page. There are notifications made for just this purpose, PSN_SETACTIVE and PSN_KILLACTIVE. --Mike-- Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber CP SearchBar v2.0.2 released

dennisV

Well, I did that, but it doesn't cover all cases I want - for example, when a user simply clicks away from my property page to another control on the form view, I want to save data he had in the pp. MCP, MCSD

dennisV

But aren't these two messages what the OnSetActive() and OnKillActive() MFC functions do? You see, I need the control to generate something when the user clicks away from it, not just changes to another property page. MCP, MCSD

RaviBee

Ah, so your property sheet is a modeless one, and is a child of your form view. You could set a timer that does what OnKillFocus() would do, each time the property sheet loses (i.e. no longer has) focus. I admit the solution reeks of cheddar, but it would work. But I think there may be something fundamentally wrong with your UI design if you need to do this. What might be more appropriate is updating your data every time the user tweaks a control within the property page(s). That way (a) you won't have to query the state of the controls and (b) your data will always be in synch with the GUI. /ravi Let's put "civil" back in "civilization" Home | Articles | Freeware | Music ravib@ravib.com

dennisV

Well, the form view has the property sheets and a grid control, so when a user clicks on something in the grid, data gets updated in the property sheets, but it has to be saved when changed in the property sheets and displayed in the grid. So, that's the problem I have - to find out when the user clicked away from the property page, so that I could update the grid BEFORE the click gets there and resets the data. I don't know if it's wrong UI design, but I couldn't think of any other way to accomplish this? But I was thinking about updating the data after each control change, but I wanted to stay away from that path for as long as possible, since I have 6 property pages with around 50 controls, so that would be a lot of handler functions :omg: MCP, MCSD

jhwurmbach

Does handling WM_SETFOCUS / WM_KILLFOCUS help you? (For me, it does not, because the controls get no WM_KILLFOCUS when the user clicks a Toolbar-button - probably the button does not accept the focus)