Inheritance and message maps/data exchanges
Posted on 2009-06-29
I'm writing an MFC app. There are many "add" and "edit" dialogs for various record types, with a lot of redundant repetition - obvious candidates for refactoring so that each inherits from a common base class.
I have concerns about mixing inheritance with MFC's message/command routing. I seemingly cannot put a messagemap or data exchange in my base class.
Must I maintain mappings and data exchanges in my derived classes? It would be convenient to push that up into the base class.