AppWizard and More in MFC - Database support, user interface, and advanced features (Page 2 of 4 )
Database support:
None – No support
Header files only – Basic support
Database view without file support - Includes database header files, link libraries, a record view, and a recordset.
Database view with file support – Add a file support to the prior option.
At last, we go to a tab where we can choose some instantly visible options. We just have to choose whether or not we want them in our application:
User Interface Features:
Thick frame - Creates a window that has a sizing border. It's default and useful.
Minimize box - The little minimize button in the right-upper corner. Default.
Maximize box – The maximize box for maximizing the window. Default.
Minimized – Open the main window as minimized at the start.
Maximized - Open the main window as maximized at the start.
System menu – If you require its presence, then put an affirmative in the box. Default.
About box – A dialog that every window has under Windows, so if you aren’t making a dialog based program, this is a mandatory option.
Initial status bar – Do we need the status bar? Default.
Split window – It will provide a splitter window like the Windows Explorer.
Toolbars:
None – We don’t want a toolbar.
Standard docking – Just a plain standard docking toolbar will be added. Default.
Browser style – The Toolbar will get a more evolved, Internet-Explorer like toolbar.
Before reaching the end, we cannot forget that there are some advanced options. To understand this you may need some superior knowledge of MFC and this article series isn’t covering that. So this part will just be mentioned. However, for a more in-depth view on each of them, don’t neglect the power of Google.
f) Advanced Features
Context-sensitive help – Generate a help file. There are two types, a WinHelp and an HTML format, but the first one isn’t supported anymore.
Printing and Print Preview – Says it all, nothing to add.
Automation - Specifies that the application can manipulate objects implemented in another application or exposes the application to Automation clients.
ActiveX controls – Supported or not. Supported by default.
MAPI (Messaging API) – Stays for e-mail handling.
Windows sockets – This stays for network connection over TCP/IP. Only needed if you are creating network capable software.
Active Accessibility - Allows you to customize the user interface for better interaction with accessibility clients.
Common Control Manifest - Generates an application manifest to enable the new Common Control DLL shipped with Microsoft Windows XP.
Number of files on recent file list – Choose how many files you want to have on the most recently used list. Anything from 0 (or none, which removes the recent file list from the menu) to 16 will go.
We finally reached the last tab. It can be described in just a paragraph. This is the place where the created classes/files names need to be confirmed. If you read the previous part, you already know which is assigned to which.
Now you have reached the end and right away AppWizard asks you if you are satisfied with the files that are to be created. In most cases, the naming is correct and you only need to confirm it. You may change the name of the header file, the implementation file, and class name, or for more advanced users, the class from which the created classes are derived.
Next: Messages and the Properties Window >>
More BrainDump Articles
More By Gabor Bernat
