Re: WM_PAINT NON-STOP IN CUSTOM CONTROL
No, Joseph.. you didn't understand me..
I've done that finally...
The idea that I wanted (do have the solution now) to use MFC (classes)
advantages and still have the ability to create your own custom control (not
owner draw)..
Custom Control is not well automated in VC MFCDialog application mode.
Create a Button, ListBox - not a big deal.. but Custom Control needs some
methodology.
That WM_PAINT non-stop - is not HOW WINDOWS WORKS (I have 10 yrs experience
of Windows programming and still don't know how Windows works ;)))..
Windows send WM_PAINT when the rectangle needs to be updated..
Non-stop, just because MFC controls all events of application and it is
non-compatible thing to use both own Win Proc Handling and MFC in one MFC
application.
I wanted to use Win 32 programming (Win Proc Handling ) + MFC classes
advantages.. that's the point.......>>!!
It's possible though, and it should be done in a proper order.
Then WM_PAINT comes only once, and mouse events come for sure, and other MFC
classes are incapsulated inside Dialog (in my case) MFC application..
If you wish to know how, tell me by mail and I'll send it to you..
Thanks for your site, was interesting to know that you like to compose music..
All the best.
Robert
vitagoni@three.com.au
"Joseph M. Newcomer" wrote:
That sounds like Windows is working in exactly the way it is designed to work. In fact,
it is following its specifications precisely. If you need to change the image, you have
to call InvalidateRect(NULL) to say that you've changed the image, otherwise there is no
reason for Windows to believe there is any need to repaint anything.
I have no idea what you mean by "sending the message func works OK", but it makes me
suspect you are doing something completely wrong.
The BeginPaint is mandatory.
WM_UPDATE does not exist. There is no such message. Surely you mean WM_PAINT.
And commenting out BeginPaint means that Windows is doing exactly what it is *supposed* to
do, which is to keep sending WM_PAINT messages until somebody redraws the window contents.
Lose the beep. You really need to understand basic Windows programming here.
See below...
On Tue, 22 Aug 2006 20:44:01 -0700, Robert <Robert@discussions.microsoft.com> wrote:
Hello Fellas,
With that BeginPaint I have the constantly receiving WM_PAINT's stopped, but
instead of updating whole region when I draw an image, it updates the only
erased rectangles or doesn't update at all if there is no dirty areas, but
the background image already changed and I need it to be full updated!!..
Loading an image function sends just one message to that image win to
WM_UPDATE and the image win callback returns 0, no problem with that
function..
Sending the message func works Ok..
But without BeginPaint it was non-stop update, so I couldn't even move the
window!!
Then I placed Beep function, just to control when the image win receives
WM_UPDATE..
And then suddenly, I commented BeginPaint/End functions and just left only
Beep..
And again I began to hear that beep non-stop again (WM_UPDATE), BUT>>>!!!!!!
Image update and window moving was fine!!!!! it works now good, exactly how
it suppose to.
So, now I placed Beep (0,1) function and no sound and perfect work..
Of course I understand that's stupid and unwell, but what can I do..???
Any Idea??
/*************************************************************/
case WM_PAINT:
// PAINTSTRUCT ps;
// BeginPaint(hwnd, &ps);
*****
hdc = BeginPaint(hwnd, &ps);
****
Beep(0, 1);
****
Lose this completely. It serves no useful purpose.
****
if (hImage != NULL)
{
HDC tmpDC;
hdc = GetDC(hwnd);
****
Lose the GetDC. You already have the correct DC from BeginPaint. This code is wrong
****
tmpDC = CreateCompatibleDC(hdc); //
GetWindowRect(hwnd, &rct);
SelectObject(tmpDC, hImage);
BitBlt(hdc, 0, 0, rct.right, rct.bottom, tmpDC, 0, 0, SRCCOPY);
DeleteDC(tmpDC);
ReleaseDC(hwnd, hdc);
****
Since the GetDC is gone, lose the ReleaseDC as well
****
}
// EndPaint(hwnd, &ps);
return 0;
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm