Solve the Problem of GDI pop-up Screen

Source: Internet
Author: User

 

Introduction

Removing flicker from an MFC application is well-covered territory. you can find the topic addressed in books, and on-line. however, the techniques presented are somewhat complicated and are usually difficult to add to an existing application. one often-presented technique is called double buffering. double Buffering allows the new screen to be drawn in off-screen memory, and then the completed screen is bit-blited back onto the physical screen.

This article presents a class calledCMemDCThat encapsulates most of the issues associated with writing to off-screen buffers. AddingCMemDCTo an existing application or MFC Active X control is nearly trivial.

Modifying an MFC application to use cmemdc
  • Add the file memdc. h in your project.
  • Add the line # include "memdc. H" to stdafx. h.
  • Add a Windows message handlerWM_ERASEBKGND.
  • Change the code in the message handler as follows: collapse
    // Change this codeBOOL CExampleView::OnEraseBkgnd(CDC* pDC) {      // TODO: Add your message handler code here and/or call default      return CView::OnEraseBkgnd(pDC);} // To this codeBOOL CExampleView::OnEraseBkgnd(CDC* pDC) {      return FALSE;}
  • Change yourOnDraw Code to the following:

    Collapse
    void CExampleView::OnDraw(CDC* dc){    CMemDC pDC(dc);    CExampleDoc* pDoc = GetDocument();    ASSERT_VALID(pDoc);    // TODO: add draw code for native data here - use pDC      //as the device context to draw to}

Compile your code after you 've made these changes and you will notice that the flicker you had seen before is gone.

Modifying a MFC Active X control to use cmemdc

To addCMemDC Support you follow the instruction for adding the support to an application, however you make one small change inOnDrawFunction.

Collapse
void CParticleTestCtlCtrl::OnDraw(CDC* pdc, const CRect& rcBounds,                                   const CRect& rcInvalid){    CMemDC pDC(pdc, &rcBounds);    // TODO: add draw code for native data here    // - use pDC as the device context to draw }

The only substantial difference is that the rcbounds is passed toCMemDCConstructor.

Source codeCollapse
#ifndef _MEMDC_H_#define _MEMDC_H_ //////////////////////////////////////////////////// CMemDC - memory DC//// Author: Keith Rule// Email:  keithr@europa.com// Copyright 1996-2002, Keith Rule//// You may freely use or modify this code provided this// Copyright is included in all derived versions.//// History - 10/3/97 Fixed scrolling bug.//               Added print support. - KR////       11/3/99 Fixed most common complaint. Added//            background color fill. - KR////       11/3/99 Added support for mapping modes other than//            MM_TEXT as suggested by Lee Sang Hun. - KR////       02/11/02 Added support for CScrollView as supplied//             by Gary Kirkham. - KR//// This class implements a memory Device Context which allows// flicker free drawing. class CMemDC : public CDC {private:           CBitmap    m_bitmap;        // Offscreen bitmap    CBitmap*       m_oldBitmap; // bitmap originally found in CMemDC    CDC*       m_pDC;           // Saves CDC passed in constructor    CRect      m_rect;          // Rectangle of drawing area.    BOOL       m_bMemDC;        // TRUE if CDC really is a Memory DC.public:        CMemDC(CDC* pDC, const CRect* pRect = NULL) : CDC()    {        ASSERT(pDC != NULL);          // Some initialization        m_pDC = pDC;        m_oldBitmap = NULL;        m_bMemDC = !pDC->IsPrinting();         // Get the rectangle to draw        if (pRect == NULL) {             pDC->GetClipBox(&m_rect);        } else {             m_rect = *pRect;        }         if (m_bMemDC) {             // Create a Memory DC             CreateCompatibleDC(pDC);             pDC->LPtoDP(&m_rect);              m_bitmap.CreateCompatibleBitmap(pDC, m_rect.Width(),                                                   m_rect.Height());             m_oldBitmap = SelectObject(&m_bitmap);              SetMapMode(pDC->GetMapMode());              SetWindowExt(pDC->GetWindowExt());             SetViewportExt(pDC->GetViewportExt());              pDC->DPtoLP(&m_rect);             SetWindowOrg(m_rect.left, m_rect.top);        } else {             // Make a copy of the relevent parts of the current              // DC for printing             m_bPrinting = pDC->m_bPrinting;             m_hDC       = pDC->m_hDC;             m_hAttribDC = pDC->m_hAttribDC;        }         // Fill background         FillSolidRect(m_rect, pDC->GetBkColor());    }        ~CMemDC()          {                  if (m_bMemDC) {             // Copy the offscreen bitmap onto the screen.             m_pDC->BitBlt(m_rect.left, m_rect.top,                            m_rect.Width(),  m_rect.Height(),                  this, m_rect.left, m_rect.top, SRCCOPY);                                      //Swap back the original bitmap.             SelectObject(m_oldBitmap);                } else {             // All we need to do is replace the DC with an illegal             // value, this keeps us from accidentally deleting the              // handles associated with the CDC that was passed to              // the constructor.                           m_hDC = m_hAttribDC = NULL;        }           }        // Allow usage as a pointer        CMemDC* operator->()     {        return this;    }            // Allow usage as a pointer        operator CMemDC*()     {        return this;    }}; #endif
License

This article, along with any associated source code and files, is licensed under the Code project open license (cpol)

About the author
Keith rule

Web Developer

United States

Member

I work at Tektronix in Beaverton or. I 've been programming for fun since 1975 (I started while in a computer explorer scout group in Spokane WA ). I 've been programming in C since 1979 and I 've been working implements sionally since 1983.

I really enjoy www.codeproject.com. It has saved me an incredible amount of time. I only hope my small contributions have given back some of what I 've taken.

 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.