- User Since
- Apr 4 2016, 7:39 AM (146 w, 1 d)
I think its now ready to land.
I'm waiting for review.
Please check updated class diagram and testcases in my previous comment.
Sun, Jan 20
Fix margin calculation
Rename Calc_Params to Calc.
Optimize chain weight calculation ( O(n^2) -> O(nlog n) )
Add testcase for chain relation.
Thu, Jan 17
Wed, Jan 16
Remove resize object again. :(
Tue, Jan 15
Remove resize object. it is unnecessary.
optimization point :)
Remove needless condition and handle -1 value.
Mon, Jan 14
Sun, Jan 13
- add more tests
- implement chain relation (efl_ui_relative_layout_example_02)
Wed, Jan 9
Rebase and remove relation_dir_to_set, relation_dir_relative_set apis.
relation_left_set(Eo *obj, Eo *child, Eo *target, double relative);
Would cover all cases passing NULL.
some patches are already applied by @Hermet except tests.
update a meson builf file
- add elementary_test example.
- rename to left, right, top, bottom.
- remove register api. (when a child have relation, it is registered)
Tue, Jan 8
You can check a text in elementary_test -to 'efl.ui.slider'with this patch.
Mon, Jan 7
Rename to Efl.Ui.Relative_Layout
Sun, Jan 6
- Rename Efl_Ui_Relative_Param -> Efl_Ui_Relative_Relation and integrate rel1 and rel2.
- (API) Rename rel1 -> left, rel2 -> right for intuitive names.
- Add Get method for properies.
- Update Class Diagram (check above comment)
Fix wrong usecase.
Fri, Dec 28
- implement margin.
- add more examples.
- add more tests.
- enhance documentations.
- implement a circular dependency check.(efl_ui_relative_example02)
- implement scale.
Dec 17 2018
Dec 16 2018
If you use aspect, max and min hints together in Efl.Ui.Box, there is wired behavior. furthermore, there is no way to use max, align(SIZE_HINT_FILL) hints together. so, i want to suggest a little idea to solve this problem.
The first is fill hint. if a widget use both hint_align(HINT_FILL) and hint_max together, there is no way to set to hint_align. (D7409)
Here is new priority with fill hint and the test cases. (D7463)
|2||HintMin + HintAspect|
Dec 3 2018
Nov 28 2018
it is weird behavior in scroller 2 elm_test.
Nov 26 2018
Nov 25 2018
It seems that this patch has no reviewers specified. If you are unsure who can review your patch, please check this wiki page and see if anyone can be added: https://phab.enlightenment.org/w/maintainers_reviewers/
Oh, this bug has happened before :(
There is strange behavior with D7300, D7311, D7347, D7348, D7353, D7349, D7350.
Test code : https://github.com/dasg34/focus_test/blob/b233a8e491fbcde1da78b5b0a4c02c8fcd078c99/test_focus.c
command: ELM_TC=1 ./test_focus
- Click 'Test button 1'
- Press Down arrow key
- Press Up arrow key.
Nov 20 2018
remove unused variable
Can you check again?
I can't reproduce that.
Please check my last comment.
There are some compiler warnings
P233 works well. Thank you :)
Because this test is related to legacy signals("focused", "unfocused"), I thought it might work on old code in order to keep backward compatibility. but there is issue to check composition focus, It is hard to ensure to consistency.
This test works well with focus manager. Thank you for the test.
Nov 14 2018
apologies, i don't remember whether we have been talking about focus and realization. you means D6737?
Because this test is written in the environment where all of top_win_focused related legacy focus API backward compatibility is broken, it is hard to say that meaningful test. if you fix that, this test will be failed.
Nov 13 2018
This problem still occurs.
- Click Unfocus gegrid button.
- Click Print focused_item button.
- I got focused item : 0x40000004b2d4 output.
I'm sorry. i don't understand this patch. can you provide the details what issue is fixed with this patch?
You just test legacy focus with focus manager. in order to check backward compatibility, it should work on legacy focus before being implemented focus manager . isn't it?