| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
ref T5361
|
| |
|
| |
|
|
|
|
|
|
| |
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D4954
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes T5410
Summary: should fix the error T5410
Reviewers: vtorri, t.naumenko, cedric, raster, an.kroitor, rimmed, NikaWhite, FurryMyad
Subscribers: artem.popov, cedric, jpeg
Maniphest Tasks: T5410
Differential Revision: https://phab.enlightenment.org/D4830
|
|
|
|
|
|
| |
It was always returning true. There is little point in returning
a bool here, an invalid scale value (eg. <= 0) wouuld lead to a
state where scale_get() != scale_set() and that's about it.
|
| |
|
|
|
|
|
|
|
|
|
| |
This API is used by elementary widgets like:
edje_object_base_scale_get(elm_layout_edje_get(ly));
This means elm_layout in fact should also expose it directly.
Ref T5315
|
|
|
|
|
|
|
|
|
| |
it seems luajit (and lua) broke api again... removed a #define from
their headers from 5.1->5.2 of lua (and seemingly luajit2.1 too). :(
this should fix T2728
@fix
|
|
|
|
|
|
|
|
|
|
|
| |
this fixes below compile warnings.
"
warning: format ‘%s’ expects argument of type ‘char *’,
but argument 3 has type ‘void *’ [-Wformat=]
printf("Successfully set the edje file: %s, group: %s\n",
file, eina_list_nth(grps, 0));
"
|
|
|
|
|
|
|
| |
eo_prefix are set to "efl_text".
Also, "Efl.Text.Format" is shortened to now include the "_format"
prefix.
"Efl.Text.Font" keeps the "_font" prefix, for better readability.
|
| |
|
|
|
|
| |
By default, multiline is disabled, so needs to enable this.
|
|
|
|
|
|
|
| |
This should later be setup through the theme.
One option will be to use global text classes.
Until the above is finalized, at least set this font and size to make
setup of the widget a bit easier.
|
|
|
|
|
|
|
| |
Also, rename the format string to 'gfx_filterstr' to match the other
strings.
Update the filter test to use this property.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following API is now supported with efl_part:
- Efl.Text.text { set; get; }
- Efl.Text.Cursor.cursor { get; }
- Efl.Text.Cursor.cursor_paragraph_first;
- Efl.Text.Cursor.cursor_paragraph_last;
- Efl.Text.Cursor.cursor_position { set; get; }
- Efl.Text.Cursor.cursor_coord_set;
- Efl.Text.Cursor.cursor_line_char_first;
- Efl.Text.Cursor.cursor_line_char_last;
- Efl.Text.Cursor.cursor_char_next;
- Efl.Text.Cursor.cursor_char_prev;
- Efl.Text.Cursor.cursor_line_jump_by;
- Efl.Text.Cursor.cursor_copy;
- Efl.Text.Cursor.cursor_content { get; }
- Efl.Text.Cursor.cursor_geometry { get; }
- Efl.Text.Cursor.cursor_text_insert;
Many of the 'part_text' functionality was moved to legacy, too.
See the edje_object.eo to see which ones are still supported.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
You now use the following:
efl_text_set(efl_part(edje_obj, "part"), "text");
const char *text = efl_text_get(efl_part(edje_obj, "part"));
The former method of edje_object_part_text_set/get is now legacy.
Also, adjusted 'tests/emotion/emotion_test_main-eo.c' with
this change.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It uses elm_layout's, where it shouldn't (it's legacy).
Also, it's not needed to to that there.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally it was its own object.
There are some valid claims that there is no justification for it to
remain an object.
Furthermore, it's apparent that it added little benefit: changes of
each cursors, in practice, triggered a query for all objects of the
same textblock. There wasn't real advantage to have a finer resolution
of controlling the cursors with their own events.
This ports back a lot of code, and changes a lot of other code in the
higher-up widgets, such as Efl.Ui.Text and co.
The usage was replaces from:
efl_canvas_text_cursor_char_next(cur_obj)
to
efl_canvas_text_cursor_char_next(text_obj, cur_obj)
that is, it is an operations on the TEXT OBJECT, rather than on the
(now removed) cursor object.
So, one less efl object to worry about now.
Hopefully, the port went smooth.
|
| |
|
|
|
|
|
|
| |
This reverts commit e9f727044b38b1e1897dc28161d355f0d18a4ecb.
This is not needed anymore as efl_debugd is now portable.
|
|
|
|
|
|
| |
This reverts commit eafe0c74e13f1a379c219e03f754f8d47e237e27.
It is not needed anymore as the daemon is now portable.
|
|
|
|
|
|
|
|
|
|
| |
The previous version of the daemon was using functions specific to
Linux, such as epoll...
The daemon communication part has been rewritten to use Ecore
functionalities.
Sorry for the inconvenience guys
|
|
|
|
|
|
|
|
|
|
|
| |
The opcodes registration request is sent directly in case the connection
is already made. Otherwise, the request is waiting for the connection to
be made by the dedicated thread (not the main loop).
That's why the request can be sent by the two different threads at the
same time, leading to send it twice. It means a callback for an opcode
would be invoked twice everytime a request with this opcode is received.
This patch fixes it by checking if the request has already been sent.
|
|
|
|
| |
otherwise the redirect is never set on the window which does not work
|
|
|
|
| |
function
|
|
|
|
|
| |
the widgets that are used to compose the naviframe are handling it, not
the naviframe itself.
|
| |
|
| |
|
|
|
|
|
| |
If there was a multiline selection that ended at the end of a line this could crash
@fix
|
|
|
|
|
|
| |
This reverts commit 0392cd3c489ee1c69dc768b2c3e8ac01ba1854c1.
oops this was supposed to just be local
|
|
|
|
|
|
|
|
|
|
| |
for compatibility reasons this can only be changed in a signal callback
in the default theme.
all themes should now use NOGRAB for parts which can be used to trigger
window_move signal bindings
ref T5552
|
|
|
|
| |
this should probably be a description-level property
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
adding an "event rect" is a common use case for rectangles, but I needed
a smarter event rect so I sent one off to school and it came back like this.
an event_grabber is a smart object which functions like a normal event rect
which has color(0,0,0,0), but with an important difference: it can have smart
members. event propagation works differently for an event_grabber:
normal:
event -> layer -> smart(obj1,obj2,obj3) ->(?) other objects
in this case, obj1,obj2,obj3 are all "inside" the smart object and their stacking
will always be considered as being inside the smart object. rendering is also
tied to the smart object in this case, as is clipping.
an event which reaches a smart object will be sent to the objects inside,
and then may continue through the smart object if there are no objects which
block repeating.
event_grabber:
event -> layer -> event_grabber -> obj1,obj2,obj3 -> STOP
in this case, obj1,obj2,obj3 are unmodified after being added to the event_grabber
and can be stacked, rendered, and clipped completely independently of the
event_grabber.
the event_grabber is considered an "event_parent" for this case. member objects
are not "inside" the event_grabber, and they are unable to receive events on
their own. instead, the event_grabber, which must be stacked above all its
members, receives events and propagates them top->down through its member objects.
if none of the member objects block the repeat of an event then the event will
still be blocked from further propagation past the event_grabber.
object lifetimes are independent of the event_grabber; deleting the event_grabber
has no effect on its members.
@feature
|
|
|
|
|
|
|
| |
_evas_event_object_list_raw_in_get() already has a null check and uses the
last list member
no functional changes
|
|
|
|
|
|
| |
slightly outdent code and prepare for pending features
no functional changes
|
|
|
|
| |
@feature
|
|
|
|
| |
This reverts commit a6fff5bc1e5e30a946e435369bcbaa406dd5d5ba.
|