VC++ Programming UESTC Chapter 12 Menus, Keyboard Accelerators, the rich Edit Control and Property sheets o Look at the command message routing system The framework checks the command message handler in one of the sequences listed here SDI App MDI App Vie View Document Document SDI main frame window MDi child frame window Application MDI main frame window A pplication The application calls only the higher level handler if there re two in different class The application can disable a menu item if it does not find a message handler for that menu item.“图表(①) menu item is disabled for this reason
VC++ Programming @ UESTC 11 ⚫ Look at the command message routing system. The framework checks the command message handler in one of the sequences listed here. The application calls only the higher level handler if there’re two in different class. The application can disable a menu item if it does not find a message handler for that menu item. “图表(T)” menu item is disabled for this reason. SDI App MDI App View View Document Document SDI main frame window MDI child frame window Application MDI main frame window Application Chapter 12 Menus, Keyboard Accelerators, the RichEdit Control and Property Sheets
VC++ Programming UESTC Chapter Twelve Menus, Keyboard Accelerators, the riched Control and property sheets e Why does the command message handler in document class not react even if we comment out the codes inside view class function? Does this not obey to the message routing rules? We need to comment out the whole message handler in view class. cpp file to make the document class do the job This proves the order in which the application framework handle command message
VC++ Programming @ UESTC 12 Chapter Twelve Menus, Keyboard Accelerators, the RichEdit Control and Property Sheets ⚫ Why does the command message handler in document class not react even if we comment out the codes inside view class function? Does this not obey to the message routing rules? We need to comment out the whole message handler in view class .cpp file to make the document class do the job!!! This proves the order in which the application framework handle command message