prevent eventual bugs.
Feel free to ask, comment, modify this tutorial.
My last commit before the end of the world.
Signed-off-by: Daniel Zaoui <daniel.zaoui@samsung.com>
SVN revision: 81425
This function was basically never working correctly. Everything was
fixed by simulating the evas_object_image_render() workflow, but
instead of actually draw we just check the pixel transparency.
Bugs fixed:
* fails when image is scaled up (could segv) or down (incorrect values);
* fails when image is moved to negative x,y;
* fails when border was being used.
Now everything is fixed and seems to work properly, except I'm not
handling the map and get_pixels() cases, these are marked with ERR()
so we can fix them if someone needs.
SVN revision: 81410
Whenever we copy an image, making it write-able
(evas_object_image_data_get(o, 1)) or just start painting a pristine
buffer (evas_object_image_size_set(o, w, h)), we must mark the image
as loaded to avoid trying to load it (and failing, marking the whole
thing as EVAS_LOAD_ERROR_GENERIC).
SVN revision: 81409
Case the real part object(rp->object) is an smart object it start to delete
the whole smart object hierarchy and a child object may be a swallow of this
real part. So just delete the rp->object after swallows got handled.
SVN revision: 81403
It's better than nothing, I don't know what the proper fix is.
FRIBIDI_CFLAGS just doesn't exist. Doesn't that macro we use call
PKG_CHECK_MODULES?
SVN revision: 81385
In ecore_wl_init(), adding wayland display fd with ECORE_FD_WRITE
flag make CPU usage 100%. The proper way to monitor the ECORE_FD_WRITE
is when the wl_display_flush() return value < 0 and errno == EAGAIN.
And if wl_display_flush() return, we remove ECORE_FD_WRITE flag from
the display fd.
Change from v1:
Add idle enterer destroy code into _ecore_wl_shutdown() to avoid
using freed wl_display.
SVN revision: 81360
Signals need to be sent with edbus_service_signal_emit() -- for basic
messages -- or edbus_service_signal_new() + edbus_service_signal_send --
for complex messages. Otherwise it's possible to send signals that are
not in the service introspection or that have different signatures by
mistake/typo.
SVN revision: 81311
having the same argument names in a D-Bus signal/method is the equivalent
in C to have a function with this signature:
int my_func(int a, int a, int a, int a);
Don't.
SVN revision: 81309
- EVAS_CALLBACK_FREE and EVAS_CALLBACK_DEL were doing the same thing
at different stages, causing a segv due double free.
- extn->file.updates and its Ipc_Data_Update were leaking.
PS: I can't backport this to 1.7, but the problem is still
there. Could someone look into those?
SVN revision: 81304
Rename these functions since they do not set the data in the
iterator/message but rather they append the data.
Also improve the documentation of edbus_message_iter_arguments_append()
to clarify its usage.
SVN revision: 81295
Daniel Zaoui
Jihoon Kim
José Roberto de Souza
Gustavo Sverzut Barbieri
Leandro Dorileo
Paulo Alcantara
Lucas De Marchi
Tom Hacohen
Carsten Haitzler
Christopher Michael
Christopher Michael
Yakov Goldberg
Stefan Schmidt
Vincent Torri
Jonas M. Gastal
Leandro Pereira