For patches which should not yet be merged
Tue, Dec 4
Update generating documentation for properties.
On a second thought... properties should have documentation :)
Mon, Dec 3
Only renaming the interfaces won't be enough. As per IRC discussion, these three properties have conflicts: Efl.Ui.Text.Text, Efl.Input.Key.Key and Efl.Input.Hold.Hold. I guess the easiest solution is to just rename either the property or the type (whatever is easier) instead of trying to come up with a clever C# trick. I'm working on a proposal.
6ec6d93535ebda03e1a4fac28b13d81b9ec79ee7 fixed make check for me.
Fri, Nov 30
Well, just renaming the interfaces wouldn't be enough, as implementing classes like Efl.Ui.Text would still conflict when they implement the interface property.
Updated version supporting interface properties.
Wed, Nov 28
Nov 5 2018
fix conflicts and rebasing commits
Nov 1 2018
Oct 22 2018
I guess problem is that scroller have focusable dummy element when it doesn't have focusable content. but it is not included in pd->iterator_list in _efl_ui_focus_manager_root_focus_efl_ui_focus_manager_border_elements_get. so, scroller can't find focusable element.
I meant focus move policy when scroller have focusable content.
The interaction problem between scroller and other widget is focus manager side issue.
Oct 21 2018
ping, scroller which have no content still can't get focus
Oct 15 2018
Update grid widget and test / examples
- update wrong grid item position calculation
- update grid test with scrolls
- update grid example to test vertical case with text
Oct 12 2018
update test cases and themes.
Oct 2 2018
update efl_ui_grid pack test in the elm_suite and add grid.edc
Sep 21 2018
Sep 18 2018
Sep 10 2018
Any other idea?
Sep 7 2018
Until someone decides what to do with this, I'm going to tag it unmergeable.
Sep 5 2018
Aug 28 2018
edit commit message
Aug 27 2018
Add @feature tag
Fix demo code
Add @deprecated tag for few config values
Add alternative config values and descriptions
Remove DO NOT MERGE for patches that should be reviewed...
Aug 26 2018
Aug 24 2018
Aug 20 2018
Could this new parameters be conflicted with belows?
I think its required, since its part of efl_alive_get().
@bu5hm4n should this be merged or should we only have the "alive" function? I do not have a strong opinion...
Aug 19 2018
Aug 17 2018
Will try this again later. :P
Something may be wrong with this that I didn't catch in initial testing.
meh. D6862 now. thanks for the help, git phab
Minor formatting fix...
I need help testing this before it can land
Aug 15 2018
I took some time to consider and explore your idea since I had been having some difficulty reconciling what you were proposing with the actual functionality required. I'll ignore your inlined comments, since they're not actually related to this patch, and are effectively proposing an entirely different approach from the one in this patch.
Aug 10 2018
see a above. i think it's simpler just done where i originally mentioned - i the time get's and select mechanism of ecore. someone also has one this "let's run time at a different speed" as an LD_PRELOAD:
Aug 9 2018
This is the total of the changes required to achieve the same sort of behavior as D6791 (although this version is consistently ~10% slower).