| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
elm_object_item_focus_set ensures that the list also gets focus, thus calling
that in _elm_list_elm_widget_on_focus_update would result in a infinite
call recursion, if setting the focus fails (for example when the object
is not visible yet, [see enlightenment for that]).
This fixes a freeze if you open lunchers config.
|
|
|
|
|
|
|
|
|
|
| |
We no longer allocate 3 buffers at startup, we now allocate only as needed.
Trimming the queue will come later, as there are some situations where we
might need 3 buffers and later drop down to 2 (when on a hardware plane)
Most clients will only ever need 2 buffers, so this is a reasonable RAM
savings.
|
|
|
|
|
| |
The buffer manager is already cleaned up at this point, don't try to
do it again.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
this leads in eo to the meaning that the manager.sub is giving
implementations to that interface, but leaving the ->func with NULL,
which leads on some maschines to the assumation that this is
pure_virtual, which means not composition objects will be queried, on
other maschines this will work, since there other inherits will
overwrite this entry and set ->src to NULL.
While i still dont understand why this works on some maschines and does
not on others, this is is now fixed.
|
|
|
|
| |
there is now a utility function
|
|
|
|
| |
this is completly not obvious. But now its documented.
|
|
|
|
|
|
|
| |
A happy thank you goes to the doc for leaving this trivial peace of
information undiscovered!
Followup commit will fix this
|
|
|
|
|
|
|
| |
_followup_previous_direction should only be called if there was a real
change to the redirect. In was happening that we have not changed the
focus but called _followup_previous_direction, which lead to weird focus
changes.
|
|
|
|
| |
calling this function was not working at all, so its gone now
|
| |
|
|
|
|
| |
the manager is in or has no focused element
|
| |
|
| |
|
|
|
|
| |
otherwise new efl_ui_focus_object_focus_get calls could be confused.
|
|
|
|
| |
the util class is for common code that is just added again and again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Conditions:
- style is "double_label"
- the is some content for items (i.e elm_label)
- elm_genlist_filter set was once called after genlist creation with
NULL data
- label_get callback uses elm_genlist_item_prev_get on its current item
- at least one item is added as a sub-item
- ~2 blocks of items are added afterwards
- items are added quickly while holding 'enter' on an elm_button
@fix
|
|
|
|
|
|
|
|
|
| |
This was broken in legacy code as well.
Thanks to @taxi2se for reporting.
elm_test -> slider -> check vertical slider
@fix
|
|
|
|
| |
Ref T6376
|
|
|
|
| |
Ref T6376
|
|
|
|
| |
Ref T6376
|
|
|
|
| |
Ref T6376
|
|
|
|
|
|
|
| |
I had eldbus_suite and eldbus_cxx_suite fail quite often for some
strange reason: name already in use... yeah but by who??? Turns out both
test cases used the same name, and when ran in parallel (make -j10
check) this would often fail.
|
|
|
|
|
| |
It keeps on failing for me, but quite inconsistently (i.e. sometimes,
not always). Annoying.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Modified index item role to EFL_ACCESS_ROLE_RADIO_MENU_ITEM from EFL_ACCESS_ROLE_PUSH_BUTTON
as index item should maintain its current state.
Test Plan:
Query the role of index item from atspi client, ATSPI_ROLE_RADIO_MENU_ITEM role should
be returned.
Reviewers: kimcinoo
Reviewed By: kimcinoo
Subscribers: cedric, govi, rajeshps, jpeg
Differential Revision: https://phab.enlightenment.org/D5486
|
|
|
|
|
| |
Proving once again that those that defeat type safety usually get what
they deserve.
|
|
|
|
|
| |
We need to destroy the buffer manager on fail, since it will exist but
only be able to create buffers we can't actually use.
|
|
|
|
| |
derp.
|
| |
|
|
|
|
|
|
|
|
|
| |
This renames 3 basic APIs specific to Win:
- name
- type
- role
Ref T5322
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The accessibility clients should not have a possibility
to dismiss popup in case when action area is set.
Reviewers: jpeg
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D5481
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: When Index item is selected, notify atspi clients.
Test Plan:
when atspi mode is enabled, item selection notification
should be received by atspi client
Reviewers: kimcinoo
Subscribers: cedric, govi, rajeshps, jpeg
Differential Revision: https://phab.enlightenment.org/D5485
|
|
|
|
|
|
|
|
| |
Summary: Try to take access name from internal entry object or text button first.
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D5480
|
|
|
|
|
|
| |
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D5479
|
|
|
|
|
|
|
|
|
| |
This thing is used by only 2 EO APIs that are marked as @beta. I wonder
if the @beta tag or the ptr() expression made it work for eolian,
because it simply wasn't defined in EO.
I'm renaming it just so that it's more consistent with the new names
used by atspi (and EO API in general).
|
|
|
|
|
|
|
|
| |
Reviewers: jpeg
Subscribers: jenkins, cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D5400
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If you want to have EFL application behave in a more efficient way. Like dropping
memory usage or stopping unecessary network operation, this option should be on
and the application should listen on PAUSE/RESUME event on the main loop.
|
|
|
|
|
|
| |
We should only open this when actually testing dmabuf. Otherwise we're
just wasting time and adding an opportunity to fail shm init over
unrelated issues.
|
|
|
|
|
|
| |
Calling this multiple times even after it fails the first time is a legit
thing now. We'll be doing that when we want to test dmabuf at connection
start.
|