But it does look and act like a selector (well, act anyway, since a selector is an abstract idea and therefore doesn't look like any specific thing). Like radio buttons, checkboxes, and option controls. the combo box is just another form of selector.bjb007 wrote:FourthWorld
As you say "The joshua tree looks like a cactus".
But don't tell me that a combobox looks or acts like a button!
That these happen to be subclassed from buttons internally may be incidental, but in the language it's helpful because the properties are 99% the same, allowing the learning to transfer what they learn from working with one selector to working with another, without having to learn an entirely different set of property names.
I agree that it may not be optimal (though we can arguably blame Apple for the fixation on "button" for selectors more than the folks at RunRev who merely seek compatibility with Apple's long-established conventions), but in the bigger picture of what to learn and how to get things done it hardly seems much of a show-stopper.