Why does my code produce an entirely black window client area colour without any display on using double bufffering to prevent flicker.

Question

0.00/5 (No votes)

See more:

I am using the double buffering method in main window of my program to prevent flickering, but I am have been getting entirely black window client area instead. What could be the problem.

The relvant codes are shown below:
Please note that the WriteDatah Function is not an actual part of the actual appliation. I created a new project and brought the problematic code to it in order to figure out was was wrong. The WriteData represent actual code in funinality. With this new test applicaion, I was able to narrow down the problem to be either the double buffering is not properly done or the mapping mode conflicts with it. What do you think.

C++

case WM_CREATE:
    {
        HDC hdc = GetDC(hWnd);

        std::tuple<double, double, int, int> Tuple = GetAppDocumentSize(hWnd, hdc, iPageWidth, iPageHeight);
        iOneMMX = static_cast<int>(Approximate(get<0>(Tuple), 0));
        iOneMMY = static_cast<int>(Approximate(get<1>(Tuple), 0));
        int iWidth = GetSystemMetrics(SM_CXSCREEN);
        int iHeight = GetSystemMetrics(SM_CYSCREEN);
        hMemDC = CreateCompatibleDC(hdc);
        hBitmap = CreateCompatibleBitmap(hdc, iWidth, iHeight);
        hOldBitmap = (HBITMAP)SelectObject(hMemDC, hBitmap);
        HBRUSH hBrush = (HBRUSH)GetStockObject(WHITE_BRUSH);
        hOldBrush = (HBRUSH)SelectObject(hMemDC, hBrush);

        ReleaseDC(hWnd,hdc);


        break;
    }

C++

case WM_PAINT:
        {
            PAINTSTRUCT ps;
            HDC hdc = BeginPaint(hWnd, &ps);
            std::tuple<double,double,int,int> Tuple = GetAppDocumentSize(hWnd, hdc, iPageWidth, iPageHeight);
          
            BitBlt(hdc, 0, 0, iPageWidth, iPageHeight, hMemDC, 0, 0, SRCCOPY);

            EndPaint(hWnd, &ps);
        }
        break;

This following code is lunched by the menu item with the ID ID_DRAW_DRAW_TEXT. So, it is handled by WM_COMMAND.

C++

case ID_DRAW_DRAWTEXT:
            {
                Rectangle(hMemDC, 0, 0, iPageWidth, iPageHeight);
                WriteDatah(hMemDC,iOneMMX,iOneMMY,iPageWidth,iPageHeight);

                InvalidateRect(hWnd, NULL, FALSE);

                break;
            }

C++

HFONT CreateAppFont(int cHeight, int cWeight, DWORD bItalic, int cEscapement, DWORD bUnderline, LPCWSTR pszFaceName)
{
    return CreateFont(cHeight, 0, cEscapement, cEscapement, cWeight, bItalic, bUnderline, FALSE, DEFAULT_CHARSET, OUT_OUTLINE_PRECIS,
        CLIP_DEFAULT_PRECIS, CLEARTYPE_QUALITY, VARIABLE_PITCH, pszFaceName);


}

C++

double Approximate(double dNumber, int iDecimalPlaces)
{
    int iMultipier = static_cast<int>(pow(10, iDecimalPlaces));
    dNumber *= iMultipier;

    double dInteger = 0.0;
    double dDecimal = modf(dNumber, &dInteger);

    int Integer = static_cast<int>(dInteger);

    if (dDecimal >= 0.5)
    {
        Integer++;
    }

    double dResult = Integer / iMultipier;

    return dResult;
}

C++

void WriteDatah(HDC hdc,int iOneMMX,int iOneMMY,int iPageWidth,int iPageHeight)
{
    UNREFERENCED_PARAMETER(iPageHeight);

    std::wstring wstData = L"Jesus is Lord of the Nations";
    
    int iOneINCHY = GetDeviceCaps(hdc, LOGPIXELSY);
    double dOneFontPOINT = (double)iOneINCHY / 72.0;
    int iOneFontPOINT = static_cast<int>(Approximate(dOneFontPOINT, 0));

    int iFontSize = 10 * iOneFontPOINT;

    HFONT hFont = CreateAppFont(iFontSize, FW_BOLD);
    HFONT hOldFont = (HFONT)SelectObject(hdc, hFont);

    int iLeft = 10 * iOneMMX;
    int iTop = 10 * iOneMMY;

    SIZE size;
    GetTextExtentPoint32(hdc, wstData.c_str(), lstrlen(wstData.c_str()), &size);
    TEXTMETRIC tm;
    GetTextMetrics(hdc, &tm);

    for (int i = 0; i < 100; i++)
    {
        TextOut(hdc, iLeft, iTop, wstData.c_str(), lstrlen(wstData.c_str()));

        iTop += tm.tmHeight + tm.tmExternalLeading;

    }
      
       


    SelectObject(hdc, hOldFont);
    
}

What I have tried:

I have been debugging all day. I have quite ab amount of googling too.

Posted 19-Jan-24 5:39am

Gbenbam

Add a Solution

Comments

Richard MacCutchan 19-Jan-24 12:36pm

I suspect that part of your problem is that you are manipulating device contexts in different parts of the code. Move all the code that deals with display issue into the WM_PAINT handler. That is how I have always done it, and never had any similar issues to this problem.

Gbenbam 19-Jan-24 20:36pm

How do you handle flickering?

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maxim Kartavenkov · Answer 1 · 2024-01-19T06:09:00

Solution 1

From the first look: you des not specify the pen and brush colors for the drawing.

Posted 19-Jan-24 6:09am

Maxim Kartavenkov

Comments

Gbenbam 19-Jan-24 20:33pm

It uses black pen and white brush.

Maxim Kartavenkov 20-Jan-24 3:59am

Check what has been draw on your compatible bitmap - you can easy save it to the file - in this case you be sure that you are on the right way. Also you can try to draw on client area first to check the results. After you should check the window styles and validate the GetLastError codes after each operation. To prevent flickering you should disable default erasing background as I already told.

Rick York · Answer 2 · 2024-01-19T07:16:00

I have used this class : Flicker Free Drawing In MFC[^] for many years and it works really well. I also wrote a non-MFC version of it that I have used a few times. Your code does not appear to use MFC but the principles are the same. It's all about handling messages, primarily WM_PAINT. However, WM_ERASEBACKGND also needs to be handled by just returning true. I recommend that you read the article carefully to see if you are doing something wrong.

Let me know if you want to see the non-MFC version and I will post it here. It's essentially the same as the MFC version except it uses GDI calls instead of CDC methods.

Gbenbam · Answer 3 · 2024-01-21T08:37:00

Whether you are using MFC or WIN32, the correct method to eliminate flickering using double buffing method is as stated below:

1. Get the window's dc.
2. Create a dc that is compartible with window's dc by using CreateCompartibleDC function and stating the window's dc as the dc to be emulated.
3. Get the width and height of the screen by using GetSystemMetrics.
4. Create a bitmap that is compartible with the window's dc of width and height equaling that o the screen's by using CreatecompartibleBitmap function and stating the window's dc as the dc to be emulated.
5. Select the bitmap created into the memory dc created by using SelectObject.
6. Get or create a brush whose colour is the same as the main window's client area background.
7. Select the created or gotten brush into the created memory dc.
8. Make the created bitmap look identical to the window's client area by painting it with the same colour the window's client area has by using PatBlt function and specifying PATCOPY in it as the copy mode.
8. Use BitBlt t transfer the content of the memory dc to the window's dc and secifying SRCCOPY as the copy mode during WM_PAINT.

Alternatively, you can use FillRect to paint the created bitmap to look like the windoW's client area. These would replace steps 6. 7. and 8.

Rather than making the created bitmap equal in size to the screen, you can make it equal in size to the client area, by calling GetClientRect, but thus would mean that you would have to repeat the entire creation process each time the window is resized. Typically you carry out your creation once and for all during WM_CREATE. Your created memory dc and bitmap variaible should be preferrably global so that they can remain in existence throughout the time the window is in existence.

Ensure you delete the memory dc and destroy the created bitmap associated with it when the window is destroyed. Typically during WM_DESTROY

Why does my code produce an entirely black window client area colour without any display on using double bufffering to prevent flicker.

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0