🚀 go-pugleaf

It's been so long since I played with dialog boxes that I'm rusty and 
I'm having trouble painting a static text control. Anyone have a clue 
as to what I am doing wrong?  (This is all API code, no VCL.)

The dialog box is a simple *.RC file dialog with a couple of static 
texts, a combo, a checkbox and three buttons.

Given
  HDC hdc = GetDC(hwnd);
  RECT rclient;
  RECT r;

  GetClientRect(hwnd, &rclient);
  r = rclient;
  r.right = somenumber; // yes, it's in range
  FillRect(hdc, &r, left_brush);
  r.left = r.right;
  r.right = rclient.right;
  FillRect(hdc, &r, right_brush);

Where left_brush is blue, CreateSolidBrush(RGB(0, 0, 128)) and
right brush is white, GetStockObject(WHITE_BRUSH)

There are white horizontal lines in the left part (when I tried a 
yellow brush for the right the white lines were there also)

So I used a memory DC and bitmap

  HDC hdcmem = CreateCompatibleDC(hdc);
  int savenum = SaveDC(hdc);
  int wide = rclient.right - rclient.left;
  int high =rclient.bottom - rclient.top;
  HBITMAP membmp = CreateCompatibleBitmap(hdc, wide, high);

  SelectObject(hdc, membmp);
  --same FillRect's as above but with memdc
  BitBlt(hdc, rclient.left, rclient,top, wide, high,
    hdcmem, 0, 0, SRCCOPY);

And now nothing is written.

However if I add this after the last FillRect in either configuration 
the number
shows just fine:

  SetBkMode(TRANSPARENT);
  char buf[32];
  wsprintf(buf, "%d", somenumber);
  TextOut(hdc, 0, 0, buf, lstrlen(buf)); // hdcmem for the other 
config

So I decided that the control must be painting its background and 
wiping out what I was doing.  To defend against that I subclassed the 
window, totally taking over WM_PAINT and WM_ERASEBKGND and doing 
CallWindowProc for all others (except for WM_DESTROY which is where I 
restore the window procedure addr with SetWindowLong but still do the 
CallWindowProc).

The results were unchanged.  Breakpoints verify that the subclassing 
code is executing.

.  Ed