Issue: horizontal list does not show correctly in desktop mode.
- The way to reproduce isssue is discribled in Task T179.
- We can also reproduce issue by runnin Ctxpopup at horizontal mode in elmentary test with standard profile.
Callbacks can be set:
- at the start of the sequence, i.e at the start of the single tap
- at the end of the sequence, i.e when mouse up occurs on long press
- when longpress is detected, i.e when mouse is still down during
longpress
if target object is deleted before GLayer is deleted, we get a crash
from _event_history_clear.
Setting target to NULL on delete, then testing it before reporting state
takes care of this problem.
Multiple popups (anchor hover and hoversel) are showing in following cases:
- Run elementary_test with Mobile profile --> Entry Anchor
+ click on anchor to show hover, then press menu key
+ right click on anchor
1. use proper local variable for entry. av -> en
2. use proper window name.
3. use proper callback function name.
4. use proper callback function prototype.
It is proper when the EVAS_CALLBACK_RESIZE is called instead of _pan_smart_resize.
When the _pan_smart_resize is called, the geometry of an object is not changed.
So the widget use the signal can miss-calculate the size.
https://phab.enlightenment.org/T133
list_itc and grid_itc are static variables, but they were managed by file_selector instance.
For example, they are allocated two times and first allocated classes are dangling
when two file selector are created.
This patch moves their init/deinit logic to constructor/destructor of file selector class.
1. call evas_object_size_hint_weight_set() before calling elm_win_resize_object_add() as documented.
2. evas_object_size_hint_align_set() is not needed for elm_win_resize_object_add().
and vice versa. Avoids some warnings in clang and it helps see that
these are actually different types.
Signed-off-by: Daniel Willmann <d.willmann@samsung.com>
elm_gesture_layer_cb_add/del functions have been added to provide this
functionality.
elm_gesture_layer_cb_set provided only one callback and so was
overriding the callback with the new one.
For ABI compatibility, some rules were needed:
- when set function is called with NULL, all the callbacks of the state will be
removed (old behavior respect)
- try to use set or add/del exclusively with a preference to the new
APIs. This is because of the first rule and because it will be more correct.
- if you remove a callback, only one instance of this callback of this
type/state for this gesture will be removed, by comparing func and data.
It means that if you register twice the same callback/data, it will be added
twice and you will have to remove also twice too.