Comments by apocalyptic.angell (Top 2 by date)

apocalyptic.angell 19-Jul-11 13:18pm View

Yeah, now that you mention that, you're probably right. I guess I'll just have to subclass the button. Oh well it was worth a shot.

apocalyptic.angell 19-Jul-11 11:27am View

I looked at those in depth before posting here. Unfortunately there is no way for me to handle the WM_SETFOCUS message that is sent to the button when it recieves focus in the dialog class of the dialog containing the button. To be able to trap it and do something about it in the dialog class I'd need to subclass the CButton class, add a handler for the WM_SETFOCUS message which would then send a message to notify the dialog class, which is what I'm hoping to avoid. I was thinking that if I could trap the WM_NEXTDLGCTL message I'd know that focus was changing and I would be able to check which control is receiving focus and preform the special actions if it's one that I'm interested in. Thanks for taking the time to help though!