Question

The WM_PAINT message

Asked by: Sandra-24

How does it work?

I find if I put a breakpoint in the WM_PAINT case, the breakpoint is hit constantly.

This means a WM_PAINT message keeps being posted, even although there seems to be no reason for painting the screen? (the window doesn't change in appearance, even with the program stopped at the breakpoint in the WM_PAINT, so not all of these paint messages are required.

Is there any way to reduce the number of redundant paint messages being posted to the message loop?

Thanks,
-Sandra

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2005-08-27 at 14:18:34ID21542362
Tags

wm_paint

,

paint

Topic

C++ Programming Language

Participating Experts
4
Points
500
Comments
13

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. WM_PAINT
    How can I get WM_PAINT to work? I was trying a little experiment that didn't quite work... can anyone shed any light? void CExpDlg::OnOK() { HDC mydc = ::GetDC(this->m_hWnd); ::LineTo(mydc,100,100); HWND hw = ::FindWindow(NULL,"My Computer"); if(hw == NU...
  2. Hook WM_PAINT Event?
    How to hook WM_PAINT of screen? I want to know where will be repaint on the screen and snap the screen changed.
  3. Hook WM_PAINT message.
    How to hook WM_Paint message? I want to snap the screen while screen is changed.

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: cwwkiePosted on 2005-08-27 at 17:40:45ID: 14769532

I know the wm_paint is at least sent when the window needs repainting. If you put a breakpoint on that, and your debugger get focussed on top of the program you are debugging, it must be repainted again after you continue. Try to call OutputDebugString instead of a breakpoint, and see what happens.

 

by: PlanetCppPosted on 2005-08-27 at 17:46:02ID: 14769548

windows does manage wm_paint differently. multiple wm_paint messages in a row are treated as one, the others are removed.

 

by: Sandra-24Posted on 2005-08-27 at 19:23:33ID: 14769730

>Try to call OutputDebugString instead of a breakpoint, and see what happens.

Ok, I will.

> windows does manage wm_paint differently. multiple wm_paint messages in a row are treated as one, the others are removed.

That's interesting to know.  I always learn so many things when I post in this forum. C++ programmers by nature have to be very close to the underlying computer and often understand thousands of valuable low-level technical details.

-Sandra

 

by: jkrPosted on 2005-08-27 at 19:39:47ID: 14769759

>>>> windows does manage wm_paint differently. multiple wm_paint messages in a row are treated as
>>>> one, the others are removed.
>>That's interesting to know.

I should add that this is done by the system, when your window proc finally receives it, the message has already "passed the tests"

 

by: Sandra-24Posted on 2005-08-27 at 19:41:13ID: 14769761

I added a OutputDebugString() in the WM_PAINT and printed an integer that I incremented every time. I timed it, in 5 seconds there were 640 WM_PAINT messages received by my application. Conservatively that's a paint message every 10 milliseconds. Painting is a fairly expensive operation in this control, I'd like to reduce that if I could. The monitor doesn't even refresh as fast as it's trying to repaint, I could show a movie at over 100 frames / sec if I could blt them that fast in the paint method.

-Sandra

 

by: jkrPosted on 2005-08-27 at 19:44:28ID: 14769764

Any operations in your code that call "InvalidateRect()" or similar functions?

 

by: Sandra-24Posted on 2005-08-27 at 20:20:06ID: 14769831

> Any operations in your code that call "InvalidateRect()" or similar functions?

Nothing like that. Here's the entire code (it's a little messy):

#include "stdafx.h"
#include "TestLargeBG.h"

#define KEY_SCANCODE(lParam) (((lParam) & 0x00FF0000)>>16)
#define KEY_REPEAT(lParam) (int)((lParam) & 0xFFFF)

// Global Variables:
HINSTANCE hInst;                                                // current instance
MSG msg;
HBITMAP bgImg;
HGDIOBJ hOldImg;
HDC hDC, hMemDC;
int width = 1000;
int height = 800;
int x = 0;
int y = 0;

int nPaints = 0;
char temp[100];

const TCHAR * szWindowClass = "TestLargeBG";        // the main window class name

// Forward declarations of functions included in this code module:
BOOL InitInstance(HINSTANCE, int);
LRESULT CALLBACK      WndProc(HWND, UINT, WPARAM, LPARAM);

HBITMAP ImageFromFile(HINSTANCE hInstance, LPCTSTR imgPath)
{
      return (HBITMAP)LoadImage(hInstance, imgPath, IMAGE_BITMAP, 0, 0, LR_LOADFROMFILE);
}

void Cleanup(HWND hWnd)
{
      ReleaseDC(hWnd, hDC);
      SelectObject(hMemDC, hOldImg);
      DeleteDC(hMemDC);
}

inline void Paint()
{
      BitBlt(hDC, 0, 0, width, height, hMemDC, x, y, SRCCOPY);
}

void KeyDown(WPARAM wParam, LPARAM lParam)
{
      int i, repeat = KEY_REPEAT(lParam);
      OutputDebugString("Key Down\n");
      switch(wParam)
      {
      case 'w':
            for(i=0; i < repeat; i++)
            {
                  y -= 4;
                  Paint();
            }
            break;
      case 'a':
            for(i=0; i < repeat; i++)
            {
                  x -= 4;
                  Paint();
            }
            break;
      case 'd':
            for(i=0; i < repeat; i++)
            {
                  x += 4;
                  Paint();
            }
            break;
      case 's':
            for(i=0; i < repeat; i++)
            {
                  y += 4;
                  Paint();
            }
            break;
      case 27: // ESC
            PostQuitMessage(0);
            break;
      }
}

int APIENTRY WinMain(HINSTANCE hInstance,
                     HINSTANCE hPrevInstance,
                     LPTSTR    lpCmdLine,
                     int       nCmdShow)
{
      // Register the window class
      WNDCLASSEX wcex;

      wcex.cbSize = sizeof(WNDCLASSEX);

      wcex.style                  = CS_HREDRAW | CS_VREDRAW | CS_OWNDC;
      wcex.lpfnWndProc      = (WNDPROC)WndProc;
      wcex.cbClsExtra            = 0;
      wcex.cbWndExtra            = 0;
      wcex.hInstance            = hInstance;
      wcex.hIcon                  = 0;
      wcex.hCursor            = LoadCursor(NULL, IDC_ARROW);
      wcex.hbrBackground      = 0;
      wcex.lpszMenuName      = 0;
      wcex.lpszClassName      = szWindowClass;
      wcex.hIconSm            = 0;

      RegisterClassEx(&wcex);

      // Load the background image
      bgImg = ImageFromFile(hInstance, "C:\\TestLargeBG.bmp");
      
      if(bgImg == NULL)
            return FALSE;

      // Perform application initialization:
      if (!InitInstance (hInstance, nCmdShow))
      {
            return FALSE;
      }

      // Main message loop:
      while (GetMessage(&msg, NULL, 0, 0))
      {
            DispatchMessage(&msg);
      }

      return (int) msg.wParam;
}

BOOL InitInstance(HINSTANCE hInstance, int nCmdShow)
{
   HWND hWnd;

   hInst = hInstance; // Store instance handle in our global variable

   hWnd = CreateWindow(szWindowClass, 0, WS_HSCROLL | WS_VSCROLL,
      CW_USEDEFAULT, 0, CW_USEDEFAULT, 0, NULL, NULL, hInstance, NULL);

   if (!hWnd)
      return FALSE;

      hDC = GetDC(hWnd);
      hMemDC = CreateCompatibleDC(hDC);
      hOldImg = SelectObject(hMemDC, bgImg);

   ShowWindow(hWnd, nCmdShow);
   UpdateWindow(hWnd);

   return TRUE;
}

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
      switch (message)
      {
      case WM_KEYDOWN:
            TranslateMessage(&msg);
            break;
      case WM_CHAR:
            KeyDown(wParam, lParam);
            break;
      case WM_PAINT:
            // Count the number of paint ops
            itoa(nPaints++,temp,10);
            temp[strlen(temp)] = '\n';
            temp[strlen(temp)] = 0;
            OutputDebugString((LPCSTR)temp);
            Paint();
            break;
      case WM_ERASEBKGND:
            return (LRESULT)1; // Do nothing, but tell windows we handled this event
      case WM_DESTROY:
            PostQuitMessage(0);
            break;
      case WM_QUIT:
            Cleanup(hWnd);
            break;
      default:
            return DefWindowProc(hWnd, message, wParam, lParam);
      }
      return 0;
}

 

by: Sandra-24Posted on 2005-08-27 at 20:26:11ID: 14769852

If you want to compile it you can create a new non-empty Win32 project in Visual Studio, put this in, and change C:\\TestLargeBG.bmp to point to a large bitmap image (mine is 3500x2400 and weighs in at 16MB.)

-Sandra

 

by: AlexFMPosted on 2005-08-27 at 23:01:17ID: 14770155

Handling WM_PAINT message we must always get window DC for painting and not to keep persistent DC as you do. Changing of the program by this way fixes the problem. Hopefully, you can continue from this point.

#include "stdafx.h"
//#include "TestLargeBG.h"
#include <stdlib.h>


#define KEY_SCANCODE(lParam) (((lParam) & 0x00FF0000)>>16)
#define KEY_REPEAT(lParam) (int)((lParam) & 0xFFFF)

// Global Variables:
HINSTANCE hInst;                                        // current instance
MSG msg;
HBITMAP bgImg;
HGDIOBJ hOldImg;
//HDC hDC, hMemDC;        // Don't use persistent HDC !!!
HDC hMemDC;
int width = 1000;
int height = 800;
int x = 0;
int y = 0;

int nPaints = 0;
char temp[100];

const TCHAR * szWindowClass = "TestLargeBG";       // the main window class name

// Forward declarations of functions included in this code module:
BOOL InitInstance(HINSTANCE, int);
LRESULT CALLBACK     WndProc(HWND, UINT, WPARAM, LPARAM);

HBITMAP ImageFromFile(HINSTANCE hInstance, LPCTSTR imgPath)
{
    return (HBITMAP)LoadImage(hInstance, imgPath, IMAGE_BITMAP, 0, 0, LR_LOADFROMFILE);
}

void Cleanup(HWND hWnd)
{
    //     ReleaseDC(hWnd, hDC);
    SelectObject(hMemDC, hOldImg);
    DeleteDC(hMemDC);
}

inline void Paint(HDC hDC)
{
    BitBlt(hDC, 0, 0, width, height, hMemDC, x, y, SRCCOPY);
}

void KeyDown(WPARAM wParam, LPARAM lParam, HWND hWnd)
{
    int i, repeat = KEY_REPEAT(lParam);
    OutputDebugString("Key Down\n");
    switch(wParam)
    {
    case 'w':
        for(i=0; i < repeat; i++)
        {
            y -= 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }

        break;
    case 'a':
        for(i=0; i < repeat; i++)
        {
            x -= 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }
        UpdateWindow(hWnd);
        break;
    case 'd':
        for(i=0; i < repeat; i++)
        {
            x += 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }
        UpdateWindow(hWnd);
        break;
    case 's':
        for(i=0; i < repeat; i++)
        {
            y += 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }
        break;
        UpdateWindow(hWnd);
    case 27: // ESC
        PostQuitMessage(0);
        break;
    }
}

int APIENTRY WinMain(HINSTANCE hInstance,
                     HINSTANCE hPrevInstance,
                     LPTSTR    lpCmdLine,
                     int       nCmdShow)
{
    // Register the window class
    WNDCLASSEX wcex;
   
    wcex.cbSize = sizeof(WNDCLASSEX);
   
    wcex.style               = CS_HREDRAW | CS_VREDRAW | CS_OWNDC;
    wcex.lpfnWndProc     = (WNDPROC)WndProc;
    wcex.cbClsExtra          = 0;
    wcex.cbWndExtra          = 0;
    wcex.hInstance          = hInstance;
    wcex.hIcon               = 0;
    wcex.hCursor          = LoadCursor(NULL, IDC_ARROW);
    wcex.hbrBackground     = 0;
    wcex.lpszMenuName     = 0;
    wcex.lpszClassName     = szWindowClass;
    wcex.hIconSm          = 0;
   
    RegisterClassEx(&wcex);
   
    // Load the background image
    bgImg = ImageFromFile(hInstance, "C:\\TestLargeBG.bmp");
   
    if(bgImg == NULL)
        return FALSE;
   
    // Perform application initialization:
    if (!InitInstance (hInstance, nCmdShow))
    {
        return FALSE;
    }
   
    // Main message loop:
    while (GetMessage(&msg, NULL, 0, 0))
    {
        TranslateMessage(&msg);
        DispatchMessage(&msg);
    }
   
    return (int) msg.wParam;
}

BOOL InitInstance(HINSTANCE hInstance, int nCmdShow)
{
    HWND hWnd;
   
    hInst = hInstance; // Store instance handle in our global variable
   
    hWnd = CreateWindow(szWindowClass, 0, WS_HSCROLL | WS_VSCROLL,
        CW_USEDEFAULT, 0, CW_USEDEFAULT, 0, NULL, NULL, hInstance, NULL);
   
    if (!hWnd)
        return FALSE;
   
    HDC hDC = GetDC(hWnd);
    hMemDC = CreateCompatibleDC(hDC);
    hOldImg = SelectObject(hMemDC, bgImg);
    ReleaseDC(hWnd, hDC);
   
    ShowWindow(hWnd, nCmdShow);
    UpdateWindow(hWnd);
   
    return TRUE;
}

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    PAINTSTRUCT ps;
    HDC hdc;
   
    switch (message)
    {
    case WM_KEYDOWN:
        TranslateMessage(&msg);
        break;
    case WM_CHAR:
        KeyDown(wParam, lParam, hWnd);
        break;
    case WM_PAINT:
        // Count the number of paint ops
        itoa(nPaints++,temp,10);
        temp[strlen(temp)] = '\n';
        temp[strlen(temp)] = 0;
        OutputDebugString((LPCSTR)temp);
       
        hdc = BeginPaint(hWnd, &ps);
        Paint(hdc);
        EndPaint(hWnd, &ps);
        break;
    case WM_ERASEBKGND:
        return (LRESULT)1; // Do nothing, but tell windows we handled this event
    case WM_DESTROY:
        PostQuitMessage(0);
        break;
    case WM_QUIT:
        Cleanup(hWnd);
        break;
    default:
        return DefWindowProc(hWnd, message, wParam, lParam);
    }
    return 0;
}

 

by: AlexFMPosted on 2005-08-27 at 23:32:01ID: 14770216

After reading your second post about keyboard handling I want to suggest you to exclude repeat counting and simplify keyboard handling code:

   // Main message loop:
    while (GetMessage(&msg, NULL, 0, 0))
    {
        TranslateMessage(&msg);
        DispatchMessage(&msg);
    }
 
...

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    PAINTSTRUCT ps;
    HDC hdc;
   
    switch (message)
    {
    case WM_CHAR:
        KeyDown(wParam, lParam, hWnd);
        break;
    case WM_PAINT:

...

void KeyDown(WPARAM wParam, LPARAM lParam, HWND hWnd)
{
    OutputDebugString("Key Down\n");
    switch(wParam)
    {
    case 'w':
        {
            y -= 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }

        break;
...

 

by: Sandra-24Posted on 2005-08-27 at 23:37:08ID: 14770228

Oh, I thought that if you pass the CS_OWNDC that you have a dedicated DC and don't need to get it from the pool and return it each time you want to paint.

That was silly of me to assume that because it appeared to work that it was working, the two are often different animals.

Thanks, Alex it works perfectly now, and no erroneous paint messages are sent.

Why the UpdateWindow() call though? Paint() is sufficient isn't it?

You not only solve the problem, but you fixed my code for me! Well beyond what I was expecting, thanks Alex. A+.

-Sandra

 

by: AlexFMPosted on 2005-08-27 at 23:51:37ID: 14770245

  case 'a':
        for(i=0; i < repeat; i++)
        {
            x -= 4;
            HDC hdc = GetDC(hWnd);
            Paint(hdc);
            ReleaseDC(hWnd, hdc);
        }
        UpdateWindow(hWnd);

Yes, you can remove UpdateWindow line.

 

by: PlanetCppPosted on 2005-08-28 at 07:19:47ID: 14771081

according to MSDN you dont need to release when you use CS_OWNDC. but you shouldnt need to use getdc. inside WM_PAINT you start with BeginPaint then end with EndPaint.
PAINTSTRUCT ps;
...
case WM_PAINT:
HDC = BeginPaint(hwnd, &ps);
....
EndPaint(hwnd, &ps);

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...