Appearance and Other Options
The fourth step in running AppWizard to create an executable Windows program (see
is to determine some of the interface appearance options for your application.
This Step 4 dialog box contains a number of independent check boxes. Check them if you
want a feature; leave them unchecked if you don't.
The fourth step of building a typical application with AppWizard is to set some interface
options.
The following are the options that affect your interface's appearance:
l Docking Toolbar. AppWizard sets up a toolbar for you. You can edit it to remove
unwanted buttons or to add new ones linked to your own menu items. This is
described in Chapter 9, "Status Bars and Toolbars."
l Initial Status Bar. AppWizard creates a status bar to display menu prompts and other
messages. Later, you can write code to add indicators and other elements to this
bar, as described in Chapter 9.
l Printing and Print Preview. Your application will have Print and Print Preview
options on the File menu, and much of the code you need in order to implement
printing will be generated by AppWizard. Chapter 6, "Printing and Print Preview,"
discusses the rest.
l Context-Sensitive Help. Your Help menu will gain Index and Using Help options, and
some of the code needed to implement Help will be provided by AppWizard. This
decision is hard to change later because quite a lot of code is added in different
places when implementing Context-Sensitive Help. Chapter 11, "Help," describes
Help implementation.
l 3D Controls. Your application will look like a typical Windows 95 application. If
you don't select this option, your dialog boxes will have a white background, and
there will be no shadows around the edges of edit boxes, check boxes, and other
controls.
l MAPI(Messaging API). Your application will be able to use the Messaging API to
send fax, email, or other messages. Chapter 18, "Sockets, MAPI, and the Internet,"
discusses the Messaging API.
l Windows Sockets. Your application can access the Internet directly, using protocols
like FTP and HTTP (the World Wide Web protocol). Chapter 18 discusses sockets.
You can produce Internet programs without enabling socket support if you use
the new WinInet classes, discussed in Chapter 19, "Internet Programming with the
WinInet Classes."
The fourth step in running AppWizard to create an executable Windows program (see
is to determine some of the interface appearance options for your application.
This Step 4 dialog box contains a number of independent check boxes. Check them if you
want a feature; leave them unchecked if you don't.
The fourth step of building a typical application with AppWizard is to set some interface
options.
The following are the options that affect your interface's appearance:
l Docking Toolbar. AppWizard sets up a toolbar for you. You can edit it to remove
unwanted buttons or to add new ones linked to your own menu items. This is
described in Chapter 9, "Status Bars and Toolbars."
l Initial Status Bar. AppWizard creates a status bar to display menu prompts and other
messages. Later, you can write code to add indicators and other elements to this
bar, as described in Chapter 9.
l Printing and Print Preview. Your application will have Print and Print Preview
options on the File menu, and much of the code you need in order to implement
printing will be generated by AppWizard. Chapter 6, "Printing and Print Preview,"
discusses the rest.
l Context-Sensitive Help. Your Help menu will gain Index and Using Help options, and
some of the code needed to implement Help will be provided by AppWizard. This
decision is hard to change later because quite a lot of code is added in different
places when implementing Context-Sensitive Help. Chapter 11, "Help," describes
Help implementation.
l 3D Controls. Your application will look like a typical Windows 95 application. If
you don't select this option, your dialog boxes will have a white background, and
there will be no shadows around the edges of edit boxes, check boxes, and other
controls.
l MAPI(Messaging API). Your application will be able to use the Messaging API to
send fax, email, or other messages. Chapter 18, "Sockets, MAPI, and the Internet,"
discusses the Messaging API.
l Windows Sockets. Your application can access the Internet directly, using protocols
like FTP and HTTP (the World Wide Web protocol). Chapter 18 discusses sockets.
You can produce Internet programs without enabling socket support if you use
the new WinInet classes, discussed in Chapter 19, "Internet Programming with the
WinInet Classes."
No comments:
Post a Comment