| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds "Efl.Ui.Text_Async" object.
This new widget uses the "async_layout" functionality of the underlying
Efl.Canvas.Text_Async object.
Currently, if "editable" mode is enabled, there is no asynchronous
layout, as interactive operations (e.g. typing) should get processed
immediately. Thus, only "non-editable" instructs the text object to do
asynchronous layout.
elementary_test "efl ui text" is modified to use this new widget.
@feature
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds Efl.Canvas.Text_Async with the 'async_layout' method.
The 'async layout' method is similar to 'size_formatted_get', but done
outside of the mainloop. When a call is made to this method, a thread
is created (after some preparation like updating the logical text
items), and the visual layout is offloaded to that thread.
Mainloop is blocked for operations that manipulate the object, if a
thread has already been created but hasn't complete its work.
Consecutive calls for async layout for the same object are not handled
simultaneously. Each time the threads has complete its work, the next
(if exists) layout will be dispatched.
@feature
|
| | |
|
| | |
|
| |
|
|
| |
avoid ambiguity
|
| |
|
|
|
| |
These error messages will be triggered when efl_part() is used, and the
part is not a swallow part.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Becuse ox is set to 0,
it cannot be negative, so negative check will be needless.
Reviewers: jpeg
Reviewed By: jpeg
Subscribers: cedric
Differential Revision: https://phab.enlightenment.org/D5155
|
| |
|
|
|
| |
Some text changes were not picked up by the Ui.Text widget, so no size
evaluation was triggered.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This reverts commit 9836116cab93388cf3d079d39180f675f86be78f.
This is based on discussion today i had.
There would be a separate minimal spinner class instead
which facilates ways to extend it.
|
| |
|
|
|
|
|
|
| |
Until now, one could not invoke functions into the constructor of a
widget possessing a parent. It is needed for widgets such as Efl.Ui.Check
where style is needed during construction.
@fix T5980
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Suppose naviframe top item is "A" and a new item "B" is newly pushed.
In this case, if "A" is deleted by elm_object_item_del() before
transition for "B" is started, then signal for "B" is also not sent and
"B" does not become visible.
The above issue happened if the transition effect was implemented by
using deferred signals (i.e. "pushed,deferred" and "popped,deferred").
To resolve the above issue, the signal only for the deleted item is not
sent.
Suppose naviframe top item is "A" and a new item "B" is newly pushed.
In this case, if "B" is deleted by elm_object_item_del() before
transition for "B" is started, then signal for "A" is still sent and "A"
becomes invisible.
To resolve the above issue, if the deleted item is the top item and it
is in the middle of item push, then all the signals related to the
deleted item are not sent.
|
| |
|
|
| |
This reverts commit 8574128b67d336e796ca0f0abc9b97e65f7799d4.
|
| |
|
|
| |
The markup information of accessible name is not necessary.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The accessible name of elm_entry was guide text.
The accessible name of elm_entry should be its text.
If there is not text information, then guide text is using for accessible name.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This is an attempt at fixing crashes in empc.
Test scenario:
ELM_ACCEL="" elementary_test -to "Gfx Filters"
And mouse scroll like crazy in the spinner.
@fix
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
On some systems we'll successfully complete the vblank ioctl but get
a reply of 0. When that happens we can't use that time for ticking
as it will break all of the entire world.
Fixes immediate screen blank on rpi3.
@ref T5977
|
| |
|
|
|
|
| |
This reverts commit e41d46c635bdf769d4b93da609883347168c719a.
This seems to be wrong
|
| |
|
|
|
|
|
|
|
| |
otherwise we might join a invalid thread id, that could lead to a
deadlock. Lets not do that.
ref T5245
@fix
|
| |
|
|
|
|
| |
since sd->bx is not an elm object, it is excluded from parent-child tree.
in case of a non-scrollable panel, the content needs to be attached to the tree
as a child of panel object directly.
|
| |
|
|
| |
Ref T5966
|
| | |
|
| | |
|
| |
|
|
|
| |
The last map point is not counted if seg is too small.
Test: change start angle to 3, the last segment is missed.
|
| | |
|
| | |
|
| |
|
|
| |
values of px0, py0 should be stored from previous command.
|
| |
|
|
|
|
|
|
| |
Well... that's just embarassing... semaphore_destroy() actually takes
the mach task as its first parameter, not the second. This core
amazingly worked very fine on macOS earlier than Sierra.
Fixes T5245
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Since some clash with old version, then add Eina_FutureXXX to their
name, later we'll sed.
|
| |
|
|
|
| |
This is actually written as efl_future_Eina_FutureXXX_then() as the
old API clashes, after removing the old code we'll "sed" to fix those.
|
| |
|
|
|
|
| |
This is a helper that creates a promise, then a future and immediately
resolves the promise, this will let the future be dispatched as usual,
from a clean main loop context.
|
| | |
|
| |
|
|
|
|
| |
This commit adds the EO support for the new future infra.
From now on there's no need to efl_future_link()/efl_future_unlink()
object and futures since the new API already handles that internally.
|
| |
|
|
|
| |
This commit adds a new promise/future API which aims to replace
efl_future.
|
| |
|
|
| |
T5966
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
When harfbuzz is enabled, _content_create_ot() function will be used
for shaping. If evas_common_font_int_cache_glyph_get() failed in some reason,
it never proceed gl_itr until the end.
It can cause weird rendering result. Because, all of gl_itr after the failure
can't have proper x_bear, y_bear and width.
@fix
Test Plan: N/A
Reviewers: raster, cedric, herdsman, jpeg
Differential Revision: https://phab.enlightenment.org/D5154
|
| |
|
|
|
|
|
|
|
|
|
| |
If current item was deleted while new item was pushed, then the signals
for the newly pushed item was not sent.
The above issue happened if the transition effect was implemented by
using deferred signals (i.e. "pushed,deferred" and "popped,deferred").
To resolve the above issue, the signals only for the deleted item is not
sent.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had here a little problem, state focus_state_eval function handled
the unregisteration and consideration of the focus flags and then only
called a helper function (which was a widget function), that then did
the registeration in logical or regular mode.
Elm scroller for example took that function overwrote it and did onyl
permit logical registrations. Then again a evaluation of the focus state
and flags took place, and the function considered elm_scroller should be
registered as regular object, but found it to be logical. This lead to
the problem that we permantently unregistered Elm.Scroller and
registered it again as logical just to unregister it again. This was on
the one side a performance downside. But also a bug since all items from
within the Elm_Scrollers sub manager are getting reparent onto the
parent, which means not the root of the scroller (the scroller itself)
is the logical entrypoint to the widget but rather this reparented
widget, which led to unexpected focus warps like described in T5923.
tldr: this fixes T5923
|
| |
|
|
|
| |
with this and the backtrace you can probebly figure out if you just
registered the same widget twice for different types
|
