on the listservers; the tech questions turn to proclamation

>> Yeah that is what I wanted, but since our Windows counterpart uses
>> a Combo Box for the same thing, we have to sue a Combo box also
>> (Mainly for Documentation and Training purposes). I have argued
>> about this, but it is not worth fighting them about as far as I am
>> concerned. I save the fights for what really matter.
>
> Hm… Well, it’s not unlikely that you could get what you’re
> looking for by implementing the “-comboBox:completedString:” and /
> or “-comboBox:indexOfItemWithStringValue:” data source methods.

Yeah I already tried these, and it does not work correctly, it puts
in the text anyway even if nothing matches.

>
> Windows is moronic in it’s use of controls that looks like combo-
> boxes where the functionality provided is actually a pop-up button.
> You can’t tell what type of control it is by looking at it. Only by
> attempting to enter some text, you’ll notice if it’s using combo
> box or pop-up button behaviour.

Yep, too bad that those morons in redmond allowed the idiots at intuit to
write quickbooks so that users could do accounting without asking apple for interface blessings.
A decade before these coders discovered the born again miracle that is OS X, the users of quick* were using completion combo boxes for quick, easy data entry.

OS X, the enhanced terminal from Cupertino