- •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.
Loading a dib into Memory
Look at the class's constructor, which is shown in Listing 11.9.
Listing 11.9 The CDib Class's Constructor
CDib::CDib(const char* fileName)
{
// Load the bitmap and initialize
// the class's data members.
LoadBitmapFile(fileName);
}
You create a CDib object by calling the CDib class's constructor with the file name of the DIB that you want to load. The constructor passes this file name to the protected member function, LoadBitmapFile(), which actually loads the bitmap. LoadBitmapFile()'s code is fairly complex. In fact, it makes up the bulk of the CDib class's code. The other CDib member functions generally return values calculated by LoadBitmapFile().
First, LoadBitmapFile() constructs an MFC CFile object:
CFile file(fileName, CFile::modeRead);
This line of code not only constructs a CFile object named file but also opens the file (whose name is passed in the fileName argument) in the read-only mode.
Next, the function declares a BITMAPFILEHEADER structure and reads the DIB's file header into the structure:
BITMAPFILEHEADER bmFileHeader;
file.Read((void*)&bmFileHeader, sizeof(bmFileHeader));
The CFile object's Read() member function requires as its arguments a pointer to the buffer in which to store the data and the size of the buffer. In this case, the buffer is the BITMAPFILEHEADER structure.
After the preceding lines, the DIB's file header is stored in the bmFileHeader structure. The first task is to check whether the opened file is actually a bitmap. The function does this (as shown in Listing 11.10) by checking the bfType member for the value 0x4D42, which is the ASCII code for the letters BM.
Listing 11.10 Checking that the File is a Bitmap
if (bmFileHeader.bfType != 0x4d42)
{ AfxMessageBox("Not a bitmap file");
m_pBmFileHeader = 0;
m_pBmInfo = 0;
m_pBmInfoHeader = 0;
m_pRGBTable = 0;
m_pDibBits = 0;
m_numColors = 0;
}
If the bfType structure member does not contain the correct value, the function sets all the class's data members to 0 and exits. Otherwise, LoadBitmapFile() calls the CFile object's GetLength() member function to get the size of the opened file:
DWORD fileLength = file.GetLength();
The function then calculates the size of the DIB by subtracting the size of the file header from the size of the file:
DWORD dibSize = fileLength - sizeof(bmFileHeader);
The program uses the resulting value, dibSize, to allocate enough memory in which to store the DIB:
BYTE* pDib = (BYTE*)GlobalAlloc(0, dibSize);
GlobalAllocPtr() is a Windows function that allocates memory and returns a pointer to that memory. It requires two arguments: a flag indicating how the memory should be allocated and the size of the memory block to be allocated. Refer to your Windows programming manual for more information on GlobalAllocPtr().
After allocating memory, the function calls the CFile object's Read() member function to read the DIB into memory and then closes the file by calling the Close() member function:
file.Read((void*)pDib, dibSize);
file.Close();
At this point, the DIB is stored in memory, and LoadBitmapFile() can now calculate the values that the class needs. The addresses of the DIB's BITMAPINFO and BITMAPINFOHEADER structures are identical, being the same address as the buffer in which the DIB is stored:
m_pBmInfo = (LPBITMAPINFO) pDib;
m_pBmInfoHeader = (LPBITMAPINFOHEADER) pDib;
The function then calculates a pointer to the color table by adding the size of the BITMAPINFOHEADER structure to the address of the DIB in memory:
m_pRGBTable =(RGBQUAD*)(pDib + m_pBmInfoHeader->biSize);
When doing this type of pointer math, be careful that you're using the correct data types. For example, because pDib is a pointer to BYTE, the number of bytes stored in biSize is added to this pointer. However, if pDib were defined as a pointer to a BITMAPINFO structure, the value biSize*sizeof(BITMAPINFO) would be added to pDib. If you don't understand this, you should review how pointer math works. Next, the function initializes the m_numColors data member, by calling the member function GetDibNumColors():
int m_numColors = GetDibNumColors();
The biSizeImage data member of the DIB's BITMAPINFOHEADER structure is filled in by calling yet another CDib member function, GetDibSizeImage():
m_pBmInfoHeader->biSizeImage = GetDibSizeImage();
Next, if the BITMAPINFOHEADER's biClrUsed member is 0, LoadBitmapFile() initializes it to the correct value, which is now stored in the m_numColors data member:
if (m_pBmInfoHeader->biClrUsed == 0)
m_pBmInfoHeader->biClrUsed = m_numColors;
Finally, LoadBitmapFile() calculates the address of the DIB's image by adding the size of the BITMAPINFOHEADER structure and the size of the color table to the pDib pointer, which contains the address of the DIB in memory:
DWORD clrTableSize = m_numColors * sizeof(RGBQUAD);
m_pDibBits = pDib + m_pBmInfoHeader->biSize + clrTableSize;
