Thanks!

Hmm that shouldn't happen :) WM_ERASEBKGND should redraw the background for the invalidated rect when the CPaintDC is created (during the internal call to BeginPaint(). Can you add a WM_ERASEBKGND that calls the base class method? Then in that handler, maybe draw a rectangle at the textrect. Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Hi, I had problems with something similar in one project. I was using static labels to show variable datas. It worked good sometimes, but not as I wanted. So I changed them with Edits, set the protection to write and erase the border (all in resource editor), then just calling SetWindowText was enough and never failed. BTW, are you erasing the background before sending the message to update screen? Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson ;)

MapWindowPoints() or ScreenToClient() CRect btnRect; btn1.GetWindowRect(btnRect); ScreenToClient(&btnRect); //assumes that this is the parent of btn1 btn1.SetWindowPos(wndTop, btnRect.left, btnRect.top, btnRect.Width(), btnRect.Height(), SWP_SHOWWINDOW);

Yes I agree with you on the interprocess communication but sm was only a suggestion. Maybe the solution requires the existence of two separate processes for some reason, then shared memory maybe a good choice. I am not arguing it will be the best though :-)