have to use a manually added rectangle to receive events. This
rectangle needs to account for framespace, else it does not receieve
events for the whole area which the bg occupies.
SVN revision: 76004
Subject: [E-devel] [patch][elementary] popup - smart theme
popup have used notify its internal widget. but popup does not take care
the notify theme in its smart_theme()
the attachment just add a line to set style to the notify and test code
also. please review and give feedback. thanks.
SVN revision: 75987
Subject: [E-devel] [patch][elementary] access - add activate callback
till now, accessibility has used ecore_x_mouse_*_send(). the patch has
activate callback which takes place of the ecore_x_mouse_*_send() stuff.
if the access module is enabled and 'double tap' is detected, elm_win
will
receive ECORE_X_ATOM_E_ILLUME_ACCESS_CONTROL message with
ECORE_X_ATOME_E_ILLUME_ACCESS_ACTION_ACTIVATE and call the activate
callback for the accessibility. that's it.
SVN revision: 75978
Subject: [E-devel] [patch] change plug-in loading behavior in elm_map
Elm_map have 3 modules (Tile, Route, Name) for plug-in loading
When elm_map is added, each 3 modules search plug-ins
(elm_map does use eina_module, not elm_module because elm_map loads
several modules. )
Previously, Each modules in elm_map search modules separately.
So module init /shutdown function in each plug-in is called 3times.
This can cause problems.
I fixed that module init is called at one time and module never be
unloaded (in process life-cycle).
SVN revision: 75974
Subject: [E-devel] [Patch] [Elementary] elm_datetime widget bug fix:
elm_datetime_field_limit_set() API is not working for min/max boundary
conditions
Hi,
Please review the attached patch for fixing issue in API
elm_datetime_field_limit_set() for boundary values.
It has been created by Sumanth for datetime widget.
[Issue Details]:
elm_datetime_field_limit_set() API is not working well for boundary
values.
[ex: for date, we can't set max limit as 31 and for minute, we can't
set 60 etc..
- it fails at boundary conditions of Min/Max limit for all
datetime fields.]
[Root cause]:
Boundary condition checking has not been done in a proper way.
[Change Description]:
Boundary checking condition is corrected and the min/max limit
boundary values are included as API input.
Signed-Off-By: Sumanth Krishna (sumanth.m@samsung.com)
Signed-Off-By: Rajeev Ranjan (rajeev.r@samsung.com)
SVN revision: 75958
On Fri, Aug 31, 2012 at 8:50 PM, Bluezery <ohpowel@gmail.com> wrote:
> Hello,
>
> Sometimes reorder animation ended incorrectly
> You can test & see the problem when background color is black and
> genlist item color is white.
> I made the added value for animation as difference between old item
> position and new item position if difference is below predefined dy.
> (y = diff, if diff < dy) So item position can be finally new item
> position at last.
> Please review this patch.
>
> Thanks
SVN revision: 75950
glview tests in Wayland:
If the preferred engine set to "opengl_x11" and we actully run on
"wayland_egl" engine, the elm_win_add will eventully use "Software FB"
engine, and no chance to use the correct engine.
Don't set the preference but let the _elm_config to determine the right
engine.
SVN revision: 75921
hooks.
The former is now issued for all scrollables, with the behavior it had
before, and the latter is a new virtual base function, with a default
implementation leading to values matching the old case where one
didn't implement the hook.
Please help me test if everything is OK -- it seems so, here.
SVN revision: 75904