| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Ref T4323
@fix
|
| | |
|
| | |
|
| |
|
|
| |
Both have been added in 1.18 not only set()
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Fixes T4338
@fix
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove EAPI symbols and functions that were
wrongfully added:
- elm_image_scale_down_set
- elm_image_scale_down_get
- elm_image_scale_up_set
- elm_image_scale_up_get
- elm_image_fill_inside_set
- elm_image_fill_inside_get
- elm_image_scale_get
- elm_image_scale_set
Fixes T4343
@fix
|
| |
|
|
|
|
|
| |
This is an internal API, should not be exposed as EAPI.
Doing this before the 1.18.x announcement.
@fix
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
EAPI elm_win_type_set
EAPI elm_win_name_set
Those two APIs should never have been part of the legacy API,
but they have been generated since at least 1.16. The commits
1aceb3bc198f3f9a07671f37564efc6657fe2a41
and
41aa19447c2a324a8cca59799a0a058fea56b575
removed the legacy symbols generation. It seemed like a good
idea since the APIs shouldn't exist, but in fact this broke
ABI. I hate this. So sorry about it.
I'm adding them back in with no documentation and as
EINA_DEPRECATED.
This is an emergency commit before the 1.18.x release
announcement.
Fixes T4344
@fix
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
if clipped color changed and not object color on image objects, then
the updates could be missed. this also fixes some corner cases where
opaqueness should not count for update deletion too. this bug seems to
have been here a while unnoticed.
fixes T4246
@fix
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit d19cd4e63caf461e28fb536968f82e0d8a365cdc.
This causes a SIGBUS error on OpenBSD when closing any application. As this
was safety patch only I will revert it for the 1.18 release and we can work
out what breaks OpenBSD here for 1.19
Fixes T4332
|
| |
|
|
|
|
|
|
| |
Not sure how this got in there, but it looks like
gbm_surface_release_buffer was being called twice on the same buffer.
This should sort out the double-free mentioned in ref T4335
Signed-off-by: Chris Michael <cp.michael@samsung.com>
|
| |
|
|
|
|
|
|
|
|
| |
alpha
If we have a borderless alpha window, then make call to set opaque
region accordingly. This still avoids calling opaque_region_set twice,
yet maintains opaque region for the above mentioned case.
Signed-off-by: Chris Michael <cp.michael@samsung.com>
|
| |
|
|
|
|
|
|
|
|
| |
combobox: add Multiple selection feature
This exposes problems with name clashes and behaviour change for the legacy API.
Revert for now and we can revisit for 1.19.
Git revert got to confused as this was committed before we merged elm in. I did
the revert manually.
|
| |
|
|
|
| |
I didn't understand well how the reusable mechanism should have be used,
now I do, and the test is not failing anymore :)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When trying to create a window, the WL EGL engine creates
an ecore_evas and connects to the wayland display. But if
EGL is not supported (in weston with nvidia for instance),
the egl initialization fails and the window must be detroyed
in order to fallback to wayland_shm.
This led to a double disconnect from the wayland display
as both the ecore_evas del and the error handling code
were trying to disconnect.
Also, use ref == 0 in two places rather than ref <= 0, as
it can prevent double frees in bad situations (ref < 0).
And reset a global variable to NULL on shutdown.
|
| |
|
|
|
|
|
|
|
|
|
| |
Simply add support for EVASGL native surfaces.
I removed all code related to OPENGL surfaces (deprecated stuff
from old Evas GL).
Fixes T2936
Note that here are still some missing features in Evas GL
support on Wayland (at least pbuffers support is not implemented).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We need elput for input handling and drm here as well. Already fixed in the
release notes but better catchup here as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This affects pointer & key events.
Here's the scenario: in Enventor, an elm_button object
grabs the up & down keys for the autocompletion feature.
But the entry will also listen to up & down to move the
cursor. Moreover, the scroller listens to up & down arrow
keys to scroll around.
So, when calling the new eo event first, the scroller
or the entry would catch it and do some action. In
Enventor, this triggered a hide on the magic anchor
object. Bad, bad.
I fear something will be wrong with this order as well.
Both events (legacy & eo) should be called simultaneously,
following the order & priorities that were set.
This being said, in real life most of EFL internals will
move to the new eo events (right now elm relies on the
new events, but edje doesn't, yet), so any app grabbing a
key probably wants to handle the event before elm. Same
for an app using focus manually.
Fixes T4310
|
| |
|
|
|
| |
This reverts commit 8cb3b79a82b1769cba5a7a10f9937aa18dd65d8a.
I shouldn't have pushed this. So wrong. Sorry about the noise.
|
| |
|
|
|
| |
Same as the previous patch in elm_widget: don't call
flags_set() if the flags have not changed.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the way the clip geometry calculation changed
(see 25d77bc1d24d9fd539c681fa58db976c1ca65051) to be
based on the bounding box rather than the raw geometry
of smart objects, the internal function
evas_object_is_in_output_rect() now returns true if the
rectangle intersects with that bounding box, even if
it's outside the raw geometry.
This breaks the drop area in E's pager, as it relies on
evas_objects_at_xy_get() to find which objects are at
this point. What I saw on my desktop was that only the
lower 10 or 20 pixels were droppable in the pager,
as maximized windows would have shadows covering the
upper 20 pixels or so.
Arguably objects_at_xy_get could also return all objects
at (x,y) including smart objects that extend beyong their
geometry. This can be added as a flag in the EO API, but
not in the legacy API.
|
| |
|
|
| |
this fixes T4318 - thanks romain.
|
| |
|
|
|
|
|
| |
This is a follow up fix for 4f840c5febe94c16627f034926cb8fdf933b465e
Due to the abbreviated use in this macro I missed this occurrence.
With this fix it passes make check as well.
|
| | |
|
