... ELM_OBJECT_SELECT_MODE_ALWAYS : This means that, even if selected, every click will make the selected callbacks be called. ...
Thu, Oct 10
code seems fine, but one question in inline.
Wed, Oct 9
Thu, Sep 26
oops. i'm late on this.
and for the notice,
me and @bu5hm4n agreed to keep multi_selectable and multi_selectable in beta,
while the selectable and single_selectale is stabilized.
hmm... I think boolean model is quite useful to userside, but still user can access boolean data by property get right?
if then it seems not serious problem in here,
at least we still have a moment to out of beta for this class in tizen side, only few weeks though.
can you land it before we release it?
if we not release door shutdown till tomorrow I can do that.
hmmm could be.
anyway we have change to make it public after released, so okay I agreed.
it has same problem iterator<ptr(uint64)> stable error.
is there any problem on iterator<ptr()>?
should we make this method @beta?
build failed by boolean_iterator_get
can you have a look and land it if its okay?
I will be offline when you online.
we are not ready for this class yet but it seems we need this factory for supporting multi-style item yet without factory customize?
add tag mvvm for issue tracking
are we have any stuff regarding this?
are we need efl-1.23 tagging still in here?
I think we should keep this task for tracking mvvm related work after 1.23 released, so remove 1.23 tag as I see we finished all 1.23 related task on this.
yes... we should fix this or at least well-explain in document, though it looks very weird that "name" cannot be name of property :p
it seems issue is solved now.
I think this task is closed by D10035
I think this task is closed by D10171
keep @beta in this released version same as T7871.
it is beta for this release version same as T7871
the mode itself is stable but it must comes with multi_selectable.
reopen task as we decide to mark it beta in this release version.
mark select_mode and multi_selectable @beta.
basic selection is completed by single_selectable,
so will discuss more about multi selection after release done.
after discussion on D10184 we decide to mark multi_selectable and multi_selectable_async as @beta for this release.
after have a look on multi_selectable_async..
I think this *should* stable for MVVM and other selected related widgets.
that is strange as it is not adding @beta but removing beta...let me have a look.
actually I think it would better to both of single_selectable and multi_selectable have common API,
like "efl_ui_selectable". is it strange? if it is strange then.. just make them be their own name is okay.
drop it as the result of dicussion in T7871
sorry for spping :p
okay than... stay current name I'll drop the patch
now only matter we take care is prefixes.
Wed, Sep 25
if we go
it is on discussion in T7871
now build is passed.
src/bindings/mono/efl_ui_item_clickable.eo.cs(502,15): error CS1591: Warning as Error: Missing XML comment for publicly visible type or member `Efl.Ui.ItemClickableClicked'
src/bindings/mono/efl_ui_item_clickable.eo.cs(506,24): error CS1591: Warning as Error: Missing XML comment for publicly visible type or member `Efl.Ui.ItemClickableClicked.Item'
and... what about event name?
EFL_UI_EVENT_SELECT_CHANGED looks fine
looks not good..
build failed. need to check more.
and single selection event name maybe?
seems we don't need this patch anymore as I tested in efl_ui_list_view_example_1
let me wait till tomorrow and no other comments, I'll drop it.
oh that is the changed "Selectable" to "Selection" on Single and Multi actually.
but we should talk about prefix also.
drop this patch as we already have collectionview in master.
yet there are remaining changes.
not sure we still need this patch or not,
let me try without this patch and if it need I'll rebase the patch.
yes. we don't know what Eina.Range will be yet,
for the future usage of Eina_Range.
if Eina_Range comes,
sorry for spamming reply,
add missing changes.
what about unselect / deselect? we go for current one?
access using deselect, that is one worry that going unselect.