- •The ministry of education and science of ukraine kharkiv national university of radio electronics
- •1. The Basics of Microsoft Foundation Classes
- •Mfc general information
- •A Framework of mfc-program
- •Creating the Application Class
- •Creating the Frame-Window Class
- •Declaring a Message Map and instantiation of application object global instance
- •Defining a Message Map
- •Messages and their processing in mfc-programs
- •Writing Message Map Functions
- •Message boxes and menus in mfc-programs
- •2. Dialog windows
- •2.1 Modal and modeless dialog windows
- •2.2 The control elements of dialog window
- •CListBox::AddString (lpctstr lpszItem ); // Call this member function to add a string (lpszItem) to a list box;
- •3. Additional control elements in mfc-programs. Working with icons, cursors, raster images
- •3.1 Additional control elements
- •Radio buttons
- •Afx_msg void cWnd::OnVScroll( uint nSbCode, uint nPos, cScrollBar* pScrollBar ); afx_msg void cWnd::OnHScroll( uint nSbCode, uint nPos, cScrollBar* pScrollBar );
- •Afx_msg void OnVScroll( uint nSbCode, uint nPos, cScrollBar* pScrollBar );
- •Working with icons, cursors, raster images
- •The icons and cursor registration
- •Icon and cursor loading
- •4. The elements of text processing in mfc
- •The redrawing problem decision
- •5. The Elements of working with graphics
- •5.1 The graphics functions.
- •Working with brushes
- •5.2 The mapping modes and output regions
- •6. Common control elements
- •Windows Common Controls
- •6.2 The toolbar using
- •On resizing, the message wm_size is sent and the standard handler OnSize() is called.
- •The working with Spins
- •The working with slider
- •To set the range (minimum and maximum positions) for the slider in a slider control use the following function:
- •The working with progress bar
- •The tree control using in mfc programs
- •Adding elements to the tree
- •The status bars usage
- •Bool cStatusBarCtrl::SetParts( int nParts, int* pWidths );
- •Tab controls using in mfc-programs
- •Int cTabCtrl::GetCurSel(); To Selects a tab in a tab control use SetCurSel() function:
- •Int cTabCtrl::SetCurSel( int nItem );
- •The property sheets and wizards
- •7. Thread multitasking and it’s implementation in mfc
- •7.1 The basic features of multitasking
- •7.2 The Synchronization
- •7.3 The working with semaphore
- •7. 4 The working with event object
- •8. The concept of Document view
- •8.1 Introduction to document conception
- •The control of documents storing
- •8.2 The dynamic creation of objects
- •The application framework creation
- •The main window and application classes creation
- •Listing 8.1 The example of main window class in Document / View concept
- •Listing 8.2 The example of document class in Document / View concept
- •8.3 The document framework creation
- •8.4 The initiation of application
- •8.5 The standard id’s, used in Document / View concept
- •9. The special types of menu and their implementation in mfc
- •9.1 The description of special menu styles
- •The mechanism to make changes in menus
- •9.2 The dynamic and floating menus implementation
- •CMenu::CreatePopupMenu
- •The example programs to work with dynamic menus
- •10. The system of help
- •10.1 The basic information on help structures
- •The call of help
- •The file of help
- •The Help file creating
- •The example of rtf file
- •10.2 The Help system including to the mfc-program
- •Parameters:
- •Return Values: If the function succeeds, the return value is nonzero. If the function fails, the return value is zero.
- •10.3 The handlers of help messages
- •The processing of help calls
- •Wm_commandhelp message processing
- •10.4 Wm_contextmenu message processing
- •11. Manipulating Device-Independent Bitmaps
- •11.1 The types of bitmap
- •11.2 The structures included to bitmap
- •Introducing the cDib Class
- •11.3 Programming the cDib Class
- •Loading a dib into Memory
- •Other cDib Member Functions
- •Creating ShowDib program
- •Modifying ShowDib's Resources
- •Adding Code to ShowDib
- •Examining the OnFileOpen() Function
- •Examining the OnDraw() Function
- •12. The elements of Database Programming
- •12.1 Understanding Database Concepts
- •Accessing a Database
- •12.2 Mfc odbc Classes
- •Registering the Database
- •Creating the Basic Employee Application
- •Creating the Database Display
- •Adding and Deleting Records
- •12.4 Sorting and Filtering
- •12.5 Odbc versus dao
- •13. Remote Automation
- •13.1 The introduction to Remote Automation
- •13.2 The Remote Automation Connection Manager and user components
- •13.3 Automation
- •Automation Clients
- •13.4 ActiveX
- •ActiveX Document Servers
- •ActiveX Document Containers
- •ActiveX Document Views
- •13.5 ActiveX Documents
- •ActiveX Controls
- •Interaction Between Controls with Windows and ActiveX Control Containers
- •13.6 Optimization of ActiveX Controls
- •13.7 Automation Servers
- •13.8 Connection Points
- •14. Microsoft DirectX and the main items of its using
- •14.2 The Component Object Model
- •IUnknown Interface
- •DirectX com Interfaces
- •DirectDraw Architecture
- •Other DirectDraw Features
- •Width and Pitch
- •14.5 Support for 3d Surfaces in DirectX
- •14.6 Direct3d Integration with DirectDraw
- •Direct3d Device Interface
- •Direct3d Texture Interface
- •The Basics of DirectDraw
- •Step 6: Writing to the Surface.The first half of the wm_timer message in ddex1 is devoted to writing to the back buffer, as shown in the following example:
- •Loading Bitmaps on the Back Buffer
- •Step 1: Creating the Palette. The ddex2 sample first loads the palette into a structure by using the following code:
- •Step 4: Flipping the Surfaces. Flipping surfaces in the ddex2 sample is essentially the same process as that in the first example. Blitting from an Off-Screen Surface
- •Step 1: Creating the Off-Screen Surfaces. The following code is added to the doInit function in ddex3 to create the two off-screen buffers:
- •Color Keys and Bitmap Animation
- •Dynamically Modifying Palettes
- •Optimizations and Customizations
- •Blitting with Color Fill
- •Determining the Capabilities of the Display Hardware
- •Storing Bitmaps in Display Memory
- •Triple Buffering
- •15. General information on OpenGl
- •15.1 Common information
- •Primitives and Commands
- •OpenGl Graphic Control
- •Execution Model
- •15.2 Basic OpenGl Operation
- •OpenGl Correctness Tips
- •15.3 OpenGl example program
- •Ph.D. Assosiate prof. Tsimbal Alexander m. System software, summary of lectures.
Examining the OnDraw() Function
Another function that you need to look at in more detail is the view object's OnDraw() function, which is responsible for updating the main window's display. In the ShowDib application, OnDraw() must display the currently selected DIB.
Because the CDib object is part of the document class, OnDraw() first gets a pointer to the CDib object, accessing the document object through the pDoc pointer supplied by OnDraw(). (The code that supplies this pointer was generated by AppWizard.) As you can see, pDoc points to the application's document object:
CDib* pDib = pDoc->m_pDib;
If the application has loaded a DIB (pDib is not 0), OnDraw() gets pointers to the DIB's image and BITMAPINFO structure:
BYTE* pBmBits = pDib->GetDibBitsPtr();
LPBITMAPINFO pBmInfo = pDib->GetDibInfoPtr();
The function also gets the DIB's width and height:
UINT bmWidth = pDib->GetDibWidth();
UINT bmHeight = pDib->GetDibHeight();
The program then displays the DIB by calling the Windows function StretchDIBits():
StretchDIBits(pDC->m_hDC, 10, 10, bmWidth, bmHeight,
0, 0, bmWidth, bmHeight, pBmBits, pBmInfo,
DIB_RGB_COLORS, SRCCOPY);
This function requires a whopping 13 arguments. The first argument is a handle to the destination device context (that is, the device context on which the DIB should be displayed). Because OnDraw() supplies a pointer to the destination device context (DC), you must use this pointer to access the DC's handle, which is stored in the DC class's m_hDC data member.
To display data, a Windows application must obtain a device context. In review, a device context is little more than a collection of attributes that describe how data should be displayed in a window. These attributes include pen colors and sizes, brush colors and sizes, fill colors, and other important graphical information.
In a normal Windows program, you'd be responsible for creating and managing a device context whenever you wanted to display something on the screen. However, Microsoft Foundation Classes takes care of much of the dirty work for you. In functions like OnDraw(), MFC supplies the device context as one of the function's parameters.
The next four arguments are the X coordinate, Y coordinate, width, and height of the destination rectangle. This rectangle is the area of the destination DC into which you want to copy the DIB. The next four arguments define the source rectangle. In this case, because you want to display the entire DIB, this rectangle has X,Y coordinates of 0,0 and is the same width and height as the DIB.
The ninth and tenth arguments are pointers to the DIB's image data and BITMAPINFO structure. The eleventh argument is a flag that describes the colors used with the DIB. The flag DIB_RGB_COLORS means that the DIB's color table contains actual RGB values, whereas the DIB_PAL_COLORS flag indicates that the color table contains 16-bit indexes into the logical palette. (You learn about logical palettes later in this chapter, in the section "Creating ShowDib, Version 2.") Finally, the last argument is a flag that tells the function how to combine the source and destination rectangles. In this case, SRCCOPY means that the source rectangle should overwrite the destination rectangle.
The StretchDIBits() function can automatically stretch or shrink the size of an image when the size of the destination surface is larger or smaller than the bitmap.
Now that you know how the program works, it's time to try it out.
The ShowDib application can now load and display a DIB. To use the program, select the File menu's Open command and select a DIB file. ShowDib loads the selected DIB and displays it in its main window.
When using this first version of ShowDib, you'll probably notice that, although the program can load and display a DIB, the resulting display sometimes looks pretty weird. This is because, currently, ShowDib ignores the DIB's color table. To display a DIB correctly, a program must create a logical palette from the DIB's color table and then select that palette before actually updating the display window. In the next section, then, you'll add palette-handling features to ShowDib so that it can display DIBs using the correct colors.
