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
found was causing compiler optimizations to, in some compielr versions
and optimization levels, to skip a func in the eva stest suites...
which is wrong. no more pure mumbo. gone entirely.
evas_textblock_string_escape_get() was the one.
SVN revision: 67266
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
Global shadow warnings are annoying and thus will be ignored at the moment,
There are other issues as well though, for example, not using cpp_token_file.
I don't know if that's intended or not, so I won't just suppress the warning.
SVN revision: 67242
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
allows us to multiple a minimim size explicitly for min size calc so
we can do things like have content slide open/closed properly.
SVN revision: 67197
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
if the eng setup has a NULL surface, and if the RenderEngine has an
existing surface, that means we are hiding/closing the window, and
thus should free the existing RenderEngine Window.
SVN revision: 67160
efficient storage with named access, can specify compare, alloc, free
and other operations for even better management.
no changelog/news as this is under eina_value, all new for 1.2 release.
SVN revision: 67155