Long time ago, in
http://www.mail-archive.com/enlightenment-devel@lists.sourceforge.net/msg32795.html
mail thread and IRC,
I talked with about problem of asynchronous event API such as
ecore_imf_context_commit_event_add,
ecore_imf_context_preedit_changed_event_add, so on.
In short, The problem is that key event and text_set APIs are processed
immediately, but commit event and preedit changed event is processed
asynchronously because those APIs add each event to ecore event queue.
To fix these problems, I've decided to create synchronous event APIs such
as ecore_imf_context_event_callback_add, del and call.
For considering compatibility, sync and async event callback functions are
used in xim and scim immodule.
SVN revision: 67290
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
cannot depend on the order in which the interfaces are given to us, so
we cannot create the data_device until we have both the input device
and the data_device_manager. Fix that.
Add more dnd code (not complete yet because frankly, the way Wayland
handles dnd & selection code is crappy, stupid, and difficult to
implement).
SVN revision: 67247
divide each new functions to two part
which create ecore evas and create socket for upper layer.
socket: new and listen
plug: new and connect
SVN revision: 67238
Subject: [E-devel] [PATCH] fix build error of ecore_imf_xim when using --disable-xim option
Date: Mon, 9 Jan 2012 19:53:17 +0900
Hello, EFL developers.
When building ecore with --disable-xim option, build error occurs.
This patch will solve this build error problem.
Would you please review and apply in svn?
SVN revision: 67191
Add more work on dnd code (incomplete still).
NB: We will need to add a method to request non-argb surfaces. For
now, all surfaces are argb.
SVN revision: 67180
After we have set the new surface for the evas engine. Reason being:
The shell_surface_listener_configure event handles resizing the
ecore_evas. If that gets called Before we have set the new engine
surface, then bad crashes can happen.
SVN revision: 67161
Add a check for valid connection in ecore_xcb_icccm.c
NB: For some reason, XCB does not like ecore's timestamp which is
being passed in. Since all the calls to ecore_x_window_focus_at_time
are being passed the current timestamp anyway, just use
XCB_CURRENT_TIME until I have more available 'free time' to dig deeper
into this.
SVN revision: 67136