Thread: GetCursor pos troubles

Okey dokey I'm having some problems with GetCursorPos, it's giving me really bad coordinates... or maybe it's something else I'm unsure.

Code:

 case WM_LBUTTONDOWN:
    {
        if(sel[0] == 1)
        {
          SetCapture(hwnd);
          GetCursorPos(&sPos);
          break;
        }
    }
    case WM_LBUTTONUP:
    {
        if(sel[0] == 1)
        {
          POINT pos;
          GetCursorPos(&pos);
          ScreenToClient(hwnd,&pos);
          ScreenToClient(hwnd,&sPos);
          DrawControl(sel[1],sPos,pos);
          ReleaseCapture();
          sel[0] = sel[1] = 0;
        }
    }

sPos is defined at the top to keep it in scope for WM_LBUTTONUP.

Are you intentionally allowing case statements to "fall through" to the next case?
Missing some "breaks" perhaps?

gg

Yeah I had fixed that after posting, it was messing up some other switch's as well ... I tried setting static POINT pos; but still it's going weird.

It's actually not realy sPos that's wrong I think, the start of the retangle is usually right but it's the width and height that are way out of whack.