The combobox (editable version) is useful when you want to present a list of possible values and you want to enter a value that is not present in the list. You can achieve this in Pivot with a TextInput + SuggestionPopup but you have no way for the user to open the list through mouse interaction (unless you add a button of course but then you have to manage 3 components in pivot where in other platforms you only have to deal with one). That is where a combo is handy but I agree that functionnaly speaking, one can use a mix of pivot controls to provide the same behaviour. Another problem is that creating a suggestion popup in pure WTKX / BXML is not very convenient (have to attach textinput listeners, etc ..), is it even possible ?
On Wed, Sep 8, 2010 at 2:21 PM, Greg Brown <[email protected]> wrote: > But let me ask this - where might you want to use a ComboBox in an > application? If we can understand the use cases for such a component, the > need for it might become more apparent. > > On Sep 8, 2010, at 8:00 AM, Greg Brown wrote: > > > We don't have any plans for a dedicated ComboBox. The non-editable > "drop-down" version (a ListButton in Pivot) seems to be used much more often > in UI design, and text fields with suggestion popups are currently a more > common way of combining stock and user-editable content. So the effort to > implement a ComboBox did not seem justified. > > G > > > > On Sep 8, 2010, at 3:49 AM, A. J. wrote: > > > >> Hi there, > >> Is there any plan to release a ComboBox control in the future ? > >> To be honest, I was fairly astonished not to see such a common control > in Pivot. > >> I know that it is possible to create its own custom contrlol (using > buttons, suggestion popup, textfield) but I guess that many persons will > have to reimplement it just because its not part of the platform. > >> What do you think ? > >> > >> AJ > >> > >> > > > >
