I think it should be our goal to get rid of this Interface, this looks very random and unspecified.

@bu5hm4n

Is this ok for following dependencies - or Do we need to remove this interface perfectly ?

1. Efl.Ui.Check implement Efl.Ui.Selectable

2. Efl.Ui.Item implements Efl.Ui.Selectable

3. efl_ui_multi_selectable.eo:29:    return: iterator<Efl.Ui.Selectable> @owned @no_unused; [[User has to free the iterator after usage.]]

4. efl_ui_radio.eo:44:      Efl.Ui.Selectable.selected {set;}

5. efl_ui_single_selectable.eo:13:       selectable : Efl.Ui.Selectable; [[The latest selected item.]]

Oh, I forgot to update this ticket, sorry. Selectable is now basically "new". The text relevant things have been refactored out, the resulting interface is *only* for selecting selectables.

We are making progress here, but I think this interface lacks a little bit of practical usage, I would like to keep it as "evaluating" for a little bit longer :)

@bu5hm4n
Thanks for sharing the current status :)

What's going on with this?

This is done ... Its now just an entity which can be selected or not. And the corresponding event for that.

There's this little thing that has been bothering me for quite some time now...
Selectable is a thing which can be selected or not.
Single_Selectable and Multi_Selectable are things which contain Selectable things inside of them.

I find it confusing and I'd rather not use the same root (Selectable) for all of them.

We discussed that before with @zmike, and it was considered understandable, because the other two names are prefixed with "Single" and "Multi".

Weak reasoning, but OK.

Anything else here ?

Not from me.

We good?

Theoretically yes, we got into a name discussion in T7871