Why the Toolbar button terminology - "command ID"

[Gary Beene]

A minor question.

Is there any particular reason why the Toolbar statement Help section uses "command id" terminology to describe a button instead of "control id", as it does for other controls?

The command id of a toolbar button is available through CB.CTL in the Callback function, just like any other control id, so it wasn't clear to me why the shift in terminology.

[José Roca]

Is there any particular reason why the Toolbar statement Help section uses "command id" terminology to describe a button instead of "control id", as it does for other controls?

Yes. Toolbar buttons aren't controls.

[Gary Beene]

Jose, thanks for the quick response!

Well enough. But still, the "command id" shows up as the value of CB.CTL.

So, CB.CTL must not supply ONLY control ids, but over values as well - in this case, "command id' values also.

That begs the obivous question - what other values (if any), does CB.CTL expose? In the Help section on CB, only the control id was discussed (only the terminology was simply "ID number"). I can't say as I recall reading of any other terminology in Help for objects that I might confuse with "control id".

Thanks again for the comment.

[José Roca]

That begs the obivous question - what other values (if any), does CB.CTL expose?

Anything that is sent to the callback function using the low word of the wParam parameter (CB.WPARAM in DDT lingo). CB.CTL is functionally equivalent to LO(WORD, wParam).