WTL is a very useful template library for Windows programming, especially for Pocket PC and SmartPhone (which do not even support MFC). But, when I implemented a multiview application on SmartPhone and Pocket PC, a block occurred. WTL cannot create a MDI project in WinCE. And, I tried to port a MDI project on the desktop; unfortunately, I failed. So, I decided to create a MDI support class myself, god bless me. It is not such difficult as what I thought initially.
I created a template class named
CMDIBase. You can inherit it from your MainFrame class, like this:
class CMainFrame : public CFrameWindowImpl<CMainFrame>,
Then add a message chain in
CMainFrame's message map:
and use functions in
SwithView to change current view to next view you want to display, and change menu and toolbar. If you set the third parameter to
TRUE, the OK button will show on the title bar, and you can handle the Command ID of
IDOK of this button.
LRESULT OnView1(WORD , WORD ,
HWND , BOOL& )
EnableUIItem to set menu item and toolbar item to Enable or Disable style. Like this:
LRESULT OnAppAbout(WORD , WORD ,
HWND , BOOL& )
The first parameter of
EnableUIItem is the resource ID of menubar, the second is the identity ID of both menu item and toolbar item.
This class is a WTL-based template class, and only for WinCE because it is not so useful if you can create a WTL MDI project on the desktop.
CMDIBase must be used in a SDI WTL project.
The motivation of making this class is to add Multiple view UI support for WinCE WTL-based projects.
It provides some functions for changing the view and menubar or toolbar related to the view. You can update the status of a command item in the menubar or toolbar. The most important thing is that it provides a more reasonable way to handle messages in the right place. It's just like in a MFC MDI project, you can handle menu commands in the related view class; not like in a WTL MDI project, where you can hardly chain a message into a view and all command messages must be handled by the mainframe.
The define of
_WINCE_SMARTPHONE in MDIBase.h is a key of changing
CMDIBase for SmartPhone and will cut same function not supported on SmartPhone.
The following list shows the main functions in
InitailToolBar: It just calls a create toolbar function and a move window function. If it does not call move window, the mainframe cannot be displayed correctly.
SwitchView: Switches to the view you want to show, and loads the related menu and toolbar.
toolbarID must be uniform.
EnableUIItem: Sets the menu item and toolbar item to enable/disable.
CUIUpdate class does not work for these, but it can set the check state correctly. So, the
setcheckstatus function is not added in