In subsequent properties, you can successfully use both IDs and indexes to identify buttons. The value of the parameter indicates that we are talking about an identifier and not about an index. If it is less than 100, then it is the index that is meant. Hence the conclusion: the number of buttons on the ruler should not exceed 100. However, this limitation does not seem excessive to me.

TBButtonEnabled[i] - button "available";

TBButtonVisible[i] - the button is visible (when you hide the button, the buttons located to the right of it are shifted to its place);

TBButtonChecked[i] - the "depressed" button (it makes sense to use only for fixed buttons, which were created with the prefix '-' or '+');

TBButtonMarked[i] - the button is highlighted (this property can also be set to true or false);

TBButtonPressed[i] - the button is "pressed";

TBButtonText[i] - the text of the label on the button;

TBButtonImage[i] - the index of the icon for the button;

TBButtonSeparator[i] - the button is "dividing" (in fact, a narrower dividing strip is depicted - flat or depressed);

TBButtonRect[i] - returns the rectangle occupied by the button on the ruler;

TBButtonWidth[i] - returns (and allows to change) the width of the button;

TBButtonAtPos(X, Y) - returns the handle of the button located on the ruler at the point with the specified coordinates (value -1 is returned if there are no buttons at this point);

TBBtnIdxAtPos(X, Y) - similar to the previous method, but returns the button index;

TBMoveButton(i, j) - moves the button with index i to position j;