MFC - the M's for Mixin
summary
MFC ships with full source and a classic single‑inheritance requirement that forces the MFC class to appear first in a base‑list, which blocks combining an MRU combo and an autofill combo when both derive from CComboBox. The concrete solution is to make template mixins that take the MFC control as a parameter so the MFC class stays first, adapt the message map macros to work with templates, and compose MRU + autofill without copy‑paste.
AI-written summary · about
chapters (4)
related talks
47mHow to painlessly migrate from MFC to Qt
30mCan you use Qt without moc?
25mSoftware Multiplexing - Share Your Libraries and Statically Link Them Too
16mDriving agentic innovation w/ MCP as the backbone of tool-aware AI
19mMELF: Multivariant Executables for a Heterogeneous World
56mIdentifying Common Code Smells
58mWhy Modules?: It's not about build time
01h 07mDesign Patterns in Modern C++