enlightenment/efl
enlightenment
/
efl
8
7
Fork 15
Code Issues 12 Pull Requests 2 Projects Releases Wiki Activity
efl/src/tests/elementary/focus_test.eo

26 lines
634 B
Plaintext
Raw Normal View History

Efl.Gfx.Entity (from Efl.Gfx) Ref https://phab.enlightenment.org/T6847 Reviewed-by: Cedric Bail <cedric@osg.samsung.com>
2018-04-05 01:47:26 -07:00
class Focus.Test(Efl.Object, Efl.Ui.Focus.Object, Efl.Gfx.Entity) {
efl_ui: introduce a focus manager and sub manager object The Efl.Ui.Focus.Manager abstracts the creation of a localization graph and a logical tree. The localization graph is used to find a object right left up or down of a given object. The logical tree is used to iterate throuw the containers which are used to build a ui. Those managers can be used bound to some layer in the ui, so for example the window is a layer, the content of a scroller is a layer. With those layers, we can make sure that movements of a scroller for example just means that this graph of objects in the scroller needs to be recalculated, and not the complete ui. The advantage of having this to layer bound datastructures is that you can easily debug those graphs, since the complete layer of this managerobject can be calculated completly.
2016-10-20 13:59:05 -07:00
methods {
elm_test_focus: resolve property name conflict
2018-02-14 18:14:52 -08:00
test_size {
efl_ui: introduce a focus manager and sub manager object The Efl.Ui.Focus.Manager abstracts the creation of a localization graph and a logical tree. The localization graph is used to find a object right left up or down of a given object. The logical tree is used to iterate throuw the containers which are used to build a ui. Those managers can be used bound to some layer in the ui, so for example the window is a layer, the content of a scroller is a layer. With those layers, we can make sure that movements of a scroller for example just means that this graph of objects in the scroller needs to be recalculated, and not the complete ui. The advantage of having this to layer bound datastructures is that you can easily debug those graphs, since the complete layer of this managerobject can be calculated completly.
2016-10-20 13:59:05 -07:00
params {
efl: Introduce Eina.Rect and switch EO APIs to it It's a complex struct but defined in EO as a simple struct. ABI-wise it's equivalent to Eina_Rectangle. Some macros that use Eina_Rectangle also work on Eina_Rect out of the box, most of the code dealing with x,y,w,h will require no modifications either. But Eina_Rect provides direct access to a size or position 2d component, as well as the usual x,y,w,h. The field "rect" is provided as a convenience for code dealing with both Eina_Rectangle and Eina_Rect. We may or may not require it. Note: Size2D could use unsigned values but I have spotted a few places in the code that actually use -1 to indicate invalid size (as opposed to 0x0). @feature
2017-09-13 19:59:44 -07:00
rect : Eina.Rect;
efl_ui: introduce a focus manager and sub manager object The Efl.Ui.Focus.Manager abstracts the creation of a localization graph and a logical tree. The localization graph is used to find a object right left up or down of a given object. The logical tree is used to iterate throuw the containers which are used to build a ui. Those managers can be used bound to some layer in the ui, so for example the window is a layer, the content of a scroller is a layer. With those layers, we can make sure that movements of a scroller for example just means that this graph of objects in the scroller needs to be recalculated, and not the complete ui. The advantage of having this to layer bound datastructures is that you can easily debug those graphs, since the complete layer of this managerobject can be calculated completly.
2016-10-20 13:59:05 -07:00
}
}
efl_ui_focus_manager: ensure the manager is in focus when focus is set this makes handling of focus easier in elementary
2017-11-14 10:46:29 -08:00
@property manager {
set {
}
values {
manager : Efl.Ui.Focus.Manager;
}
}
efl_ui: introduce a focus manager and sub manager object The Efl.Ui.Focus.Manager abstracts the creation of a localization graph and a logical tree. The localization graph is used to find a object right left up or down of a given object. The logical tree is used to iterate throuw the containers which are used to build a ui. Those managers can be used bound to some layer in the ui, so for example the window is a layer, the content of a scroller is a layer. With those layers, we can make sure that movements of a scroller for example just means that this graph of objects in the scroller needs to be recalculated, and not the complete ui. The advantage of having this to layer bound datastructures is that you can easily debug those graphs, since the complete layer of this managerobject can be calculated completly.
2016-10-20 13:59:05 -07:00
}
implements {
Efl.Object.constructor;
efl_ui_focus_manager: rename api from geometry to focus_geometry otherwise we would clash with efl.gfx.
2017-04-30 01:57:56 -07:00
Efl.Ui.Focus.Object.focus_geometry { get; }
elementary: fix focus tests
2017-04-19 05:10:43 -07:00
Efl.Ui.Focus.Object.focus { set; }
efl_ui_focus: merge efl_ui_focus_user and efl_ui_focus_object into one mixin Summary: focus_user and focus_object are similar classes. by merging them into one mixin, we can maintain consistency. Test Plan: make check Reviewers: bu5hm4n Subscribers: cedric, Jaehyun_Cho, woohyun, jpeg Differential Revision: https://phab.enlightenment.org/D5734
2018-01-16 12:17:11 -08:00
Efl.Ui.Focus.Object.focus_manager { get; }
Efl.Ui.Focus.Object.focus_parent {get; }
Efl.Gfx.Entity (from Efl.Gfx) Ref https://phab.enlightenment.org/T6847 Reviewed-by: Cedric Bail <cedric@osg.samsung.com>
2018-04-05 01:47:26 -07:00
Efl.Gfx.Entity.geometry { get; }
efl_ui: introduce a focus manager and sub manager object The Efl.Ui.Focus.Manager abstracts the creation of a localization graph and a logical tree. The localization graph is used to find a object right left up or down of a given object. The logical tree is used to iterate throuw the containers which are used to build a ui. Those managers can be used bound to some layer in the ui, so for example the window is a layer, the content of a scroller is a layer. With those layers, we can make sure that movements of a scroller for example just means that this graph of objects in the scroller needs to be recalculated, and not the complete ui. The advantage of having this to layer bound datastructures is that you can easily debug those graphs, since the complete layer of this managerobject can be calculated completly.
2016-10-20 13:59:05 -07:00
}
elementary: fix focus tests
2017-04-19 05:10:43 -07:00
}