MakePoints

[Cliff Nichols]

I had not thought about choice of format.

one of those "lil things" that could cause "Such Problems" later

maybe LO should be match with LONG rather than DWORD so negative values match???

[Patrice Terrier]

Common mistake with mouse coordinates and control ID

[Dominic Mitchell]

Just do this

MACRO MAKEPOINTS(lParam, pt)
    pt.x = LOINT(lParam)
    pt.y = HIINT(lParam)
END MACRO

The result is the same.
Why did you use loword?

[Michael Mattias]

Probably NOT an oversight...
From Windef.h

typedef struct tagPOINTS
{
#ifndef _MAC
    SHORT   x;
    SHORT   y;
#else
    SHORT   y;
    SHORT   x;
#endif
} POINTS, *PPOINTS, *LPPOINTS;

from wingdi.h

#define MAKEPOINTS(l)       (*((POINTS FAR *)&(l)))

I think your conversion is fine.

[José Roca]

It is not an oversight. It simply can't be translated because it returns an structure and neither PB macros nor PB functions can currently do it.

POINTS MAKEPOINTS(
    DWORD dwValue
);

You are using a workaround, not a straight conversion.

[Cliff Nichols]

Temporarily I am using

MACRO MAKEPOINTS(lParam, pt)
    pt.x = BITS%(LOWRD(lParam))
    pt.y = BITS%(HIWRD(lParam))
END MACRO

But since docs state for WM_MOUSEMOVE

Remarks

The MAKEPOINTS macro can be used to convert the lParam parameter to a POINTS structure.

My compiler says MakePoints is undefined unless I use the macro above. So I have to ask if this is an oversight in the Win32Api.Inc file???? or am I missing an Inc that already has this macro??/