Sixting, what's the name of mfc now

MFC under windows is not out of date. The reason why MFC created the message mechanism is to realize its trinity framework of frame/view/document. The significance of frame/view/document architecture is to assign the responsibility of processing messages to reasonable classes for processing. For example, if you click the "Save" option on the menu, the message will be handed over to the Doc class for implementation, while it is more convenient to click the "Update" option to hand over the message to the View class for processing. The message mechanism of MFC is responsible for passing the message to the appropriate class for processing. The following explains the realization idea of message mechanism: 1. Compare the idea with the message table: establish a message table for each class, which contains the messages that this class can handle, and the messages and their processing functions also correspond to each other one by one. In this way, you can traverse the message table and compare it to see which messages this class can handle, and you can create a message handling function. 2. Traversal thinking: To make the messages generated in the framework be processed in the Doc class, the thinking is also simple traversal: first, see if there is anything that can be processed in the view, if not, then see if it can be processed in your own class, if not, then see if there is a corresponding processing function in the Doc class. 3.Frame/View/Doc Trinity: I don't really remember. It seems that if you create a frame, you will create its corresponding view and Doc (in the case of a single document, it seems that you will create multiple documents). So you can find the corresponding document through the above view.