Listbox_SetSel macro

[Bill Scharf]

Just a curious thought--

Why is the Listbox_SetSel macro have parameters in a different order than MS's documentation?
My commctrl.inc has


#IF %DEF(%USEMACROS)
MACRO Listbox_SetSel (hListBox, fSelect, index) = SendMessage(hListBox, %LB_SETSEL, fSelect, index)
#ELSE
FUNCTION Listbox_SetSel (BYVAL hListBox AS DWORD, BYVAL fSelect AS LONG, _
BYVAL index AS LONG) AS LONG
FUNCTION = SendMessage(hListBox, %LB_SETSEL, fSelect, index)
END FUNCTION
#ENDIF


http://msdn.microsoft.com/en-us/libr...59(VS.85).aspx has

int ListBox_SetSel(
HWND hwndCtl,
int index,
BOOL fSelect
);


This is no big deal; I am just wondering why this is.

Any thoughts?

[Michael Mattias]

My API doc for LB_SETSEL message has wParam=flags, lparam=index, meaning the PB-created macros and functions arej just fine.

LsitBox_SetSel (at microsoft link provided) is documented to be a MACRO. Since you don't have the source code used to convert that Microsoft Macro to an appropriate SendMesssage call, you don't know how its done and it's possible Microsoft's "macro writer" was in a strange mood when he did that. (i.e, careless)

The bottom line is, you can't assume Microsoft created macros the same way PowerBASIC Inc. created macros.

[José Roca]

Why is the Listbox_SetSel macro have parameters in a different order than MS's documentation?

Because the MSDN documentation is wrong.

The definition of the macro, included in WindowsX.h, is as follows:

#define ListBox_SetSel(hwndCtl, fSelect, index)     ((int)(DWORD)SNDMSG((hwndCtl), LB_SETSEL, (WPARAM)(BOOL)(fSelect), (LPARAM)(index)))

[Bill Scharf]

Thanks! It is always nice to see examples of PB being more "on the ball" than M$