We have to subtract the framespace offset from the current set pointer
object, otherwise it will have that offset added to it when
evas_object_move() is done on it. This happens because the pointer
object has no parent, and is not marked with the flag "is_frame".
SVN revision: 78972
frame if the option has not been specified. This means that if we want
a more complex frame (think elm windows), then we need to set this
flag to 0.
SVN revision: 75498
The challenge here is that the native window representation is stored
in Ecore_Evas's prop.window. But currently there is no checking of
what driver the Ecore_Evas is for when calls are made to e.g.
ecore_evas_software_x11_window_get.
The attached change to Ecore makes the appropriate functions return 0
or NULL if the driver for the Ecore doesn't match as expected. This
can then be used to identify if an Ecore_Evas is e.g. from X11 or from
Wayland.
SVN revision: 71453
Subject: [E-devel] [patch] ecore doxygen doc (2)
Date: Thu, 12 Apr 2012 12:46:04 +0900
Hi,
This is a big patch. It fixes:
- undef #EINA_{TRUE,FALSE} links
- @c for NULL and EINA_{TRUE,FALSE}
- some formatting/spello
- several missing return types
SVN revision: 70117
Subject: [E-devel] ecore_evas typedef patch src/lib
the attached patch adds
typedef void (*Ecore_Evas_Event_Cb) (Ecore_Evas *ee);
in Ecore_Evas.h and ecore_evas_private.h
Ecore_Evas_Event_Cb is then used within :
ecore_evas.c
ecore_evas_psl1ght.c
ecore_evas_win32.c
ecore_evas_wince.c
ecore_evas_x.c
SVN revision: 68140
Hello e people, i modified some comments to get less doxygen
warnings/errors.
Signed-Off-By: Guillaume Friloux <guillaume.friloux@asp64.com>
SVN revision: 67270
The reson why I add this is for communicate with X in async mode.
For example, If applications call elm_win_rotation_with_resize_set API
when they start run and rotation mode is set.
ecore size doesn't changed yet, so it make elm window size to 1
becaues elm window's resize function use ecore_evas_geometry_get API.
so I add new api help upperside get info related with recently request geometry
SVN revision: 64492
Nothing changes, only making the ecore fb engine to send keyboard and
mouse events using ecore_input_evas, instead of its own ecore events.
Patch for SiT.
SVN revision: 64447
EWS is a new Ecor_Evas engine that builds on top of other engines. It
will create a backing store Ecore_Evas and ecore_evas_ews_new()
windows are created in it as images, but transparent to the outside
users (similar to buffer's ecore_evas_object_image_new()).
It provides a basic windowing system, with a known background object
that can be changed to your pleasure, and issue Ecore_Events to notify
of new windows and changes like movement, etc. Then you can write a
simple window manager based on it. (See example, Elementary will
contain one as well).
Backing store is determined by your best engine (as in
ecore_evas_new()) or specified with ecore_evas_ews_engine_set() or
environment variable $ECORE_EVAS_EWS (format:
engine-name❌y:w:h:options). The size can be set with
ecore_evas_ews_setup().
SVN revision: 63848
These functions are not contemplated by examples because there is no
meaningfull example(just setting the flags doesn't won't help developers
in understading how to use them) and because their behavior is dependant
on the windowing system.
SVN revision: 62056
Subject: [E-devel] XRender engine causes ecore build failure
while building ecore. The problem is that this engine was removed from evas
but not yet completely from ecore. I was on IRC with Vincent Torri (vtorri)
and Daniel Juyung Seo (SeoZ) and the consensus was to remove the code for the
XRender engines, both the Xlib and XCB versions.
There is a switch over the different engine types, where there are still a few
places left where XRender is handled, grep for "xrender" or "XRENDER" and you
will find them. The question is whether to just return NULL in order to signal
that this engine is not supported or to remove the whole thing. The latter
could break binary compatibility, therefore I left those stubs in.
SVN revision: 60502
This common interface allows engines to provide whole screen
information to users.
Right now just X is implemented and it queries the size of the default
screen. I hope this is fine.
SVN revision: 59761
Rafael Antognolli
Carsten Haitzler
Eduardo Lima (Etrunko)
Christopher Michael
Jihoon Kim
Daniel Juyung Seo
Jérôme Pinot
Cedric BAIL
Jérémy Zurcher
Guillaume Friloux
Youness Alaoui
Nicolas Aguirre
Jiyoun Park
Gustavo Sverzut Barbieri
Vincent Torri
Sebastian Dransfeld
Jonas M. Gastal
Gustavo Lima Chaves
Ulrich Eckhardt