Wish [B4X] B4XComboBox ValueMember and DisplayMember

[LucaMs]

Not rarely (mainly in DBs managements) you need a ComboBox in which an Item is made of a display value and a diffent associated value, i.e. a "description field" of a table and the relative primary key (usually the classic Integer ID).

I found the B4XComboBox source code here but I know also that B4XComboBox is part of XUI Views.

What should I do? Just waiting?

 

[walt61]

+1

Indeed, when the combobox is sorted and its items can be localised, that would simplify things as the localisation may change the order in which items appear.

 

[Erel]

This is really trivial to implement in your code. Just add a Map that maps between the items and the values you like.

 

[walt61]

Sure, and that's how I'm doing it indeed

 

[LucaMs]

I modified B4XComboBox.bas so that it is possible to have what I was asking for, despite not having used those names (ValueMember and DisplayMember, as in VB Net). I also added two methods, to add a single item and to remove one.

I attach the .bas file (zipped) and the XUI Views.b4xlib library that I have updated to version 2.30.

These changes must first be approved by Erel.

[Erel, all my changes are signed with 'LM]


B4J example (but note that the main reason for my changes is to be able to make the best use of the B4XComboBox with DBs tables).

P.S. Added another method: GetItemValue(Index As Int).


NOT APPROVED, FILES REMOVED.

 

[Erel]

It will not be added to XUI Views.
It is trivial to implement this map in your own code and there are several problems with your code:

1. Adding two events to a nice and simple class is a bad idea.
2. Things will break if the user adds multiple items with the same "key".

 

[LucaMs]

It will not be added to XUI Views.

So it is better that I remove the 2 files attached.

It is trivial to implement this map in your own code

Sure but:
1 - it is not so trivial for beginners
2 - if it is already done internally, the user-programmer needs to do less work

1. Adding two events to a nice and simple class is a bad idea.

All objects have more than one event.

2. Things will break if the user adds multiple items with the same "key".

I haven't tested the code much, since I knew that I would have to submit it to you, but I think I have avoided duplicate keys; i will check this.


So I will use the source of the class and make it a library just for me (with a different name).

 

[Erel]

So I will use the source of the class and make it a library just for me (with a different name).

You can follow the approach I follow with xCLV and create an extension class. The developer will pass B4XComboBox to your class and from that point will only use your class to access the items. This will give you freedom to extend it in many ways.

 

[LucaMs]

You can follow the approach I follow with xCLV and create an extension class. The developer will pass B4XComboBox to your class and from that point will only use your class to access the items. This will give you freedom to extend it in many ways.

I don't think I can do it.

Within my class, I cannot intercept the CmbBox_SelectedIndexChanged event or the setSelectedIndex setting, from the original B4XComboBox passed as argument to the class initialization.

 

[LucaMs]