widget hierarchy.
Win inherits directly from Elm_Widget_Smart_Class, while inwin is now
an elm layout.
Note that elm_widget_sub_object_list_get(), which was an unecessary
hack only used on win, was killed.
SVN revision: 70640
Current Issue:
Currently when we add a widget to window as a sub-object, e.g.
elm_notify_add(win) which internally calls elm_widget_sub_object_add
then the focus chain using <TAB> includes only
the first focusable subitem of the widget, not all.
Whereas with elm_win_resize_object_add, it works fine and cycles to
all focusable sub-items of the widget.
Reason:
The reason is that we are appending sub-object to the list in
elm_win which is used for focus chain, only in case of
elm_win_resize_object_add.
Change Description:
Added a new API: EAPI Eina_List
*elm_widget_sub_object_list_get(const Evas_Object *obj);
This API returns the list of sub-objects of an elementary widget
(sd->subobjs) where sd is Smart_Data pointer obtainted using
elm_widget_smart_data_get(obj).
We have used this API in elm_win for focus_next_hook implementation.
Signed-Off-By: RAJEEV RANJAN<rajeev.r>@samsumg.com>
SVN revision: 69943
Subject: [E-devel] [Patch] Ecore, Elementary: Supporting indicator
opacity mode
This is Myoungwoon Roy Kim.
This patches are for supporting the indicator's opacity mode and made by
Jeonhoon Park(jh1979.park@samsung.com) who is responsible for Indicator
application.
Requirements:
- In mobile device, Indicator area should be displayed as Opacity,
Transparency, or sometimes Translucency according to the UX
requirements.
This requirement can be applied in case of fullscreen based menu and
fullscreen applications like video player etc.
Functional requirements:
1. User can set indicator's opacity mode as opacity, transparency, and
translucency
2. User can get the current indicator's opacity mode.
Currently there are no APIs for supporting the upper functional
requirements.
Thus, he added support for indicator's opacity mode.
It is designed for EFL developers easily to set the indicator's opacity
like the existing indicator's mode.
He added a Elm_Win_Indicator_Opacity_Mode structure variable into
Elm_Win
structure.
Meanwhile, new two APIs are implemented independently from the existing
source code.
Anybody please review this and apply it to upstream code.
SVN revision: 68959
Subject: [E-devel] [Patch][elm_win] elm_win_title_set(); can make a
crash with NULL
Have ever try to call elm_win_title_set(win, NULL)? Then try... :-] It
makes "Segmentation Fault".
Yeah, we can add patch in the Ecore side, but we can prevent the
segmentation fault before go inside.
Please check the patch and give any feedbacks. Thanks a lot.
SVN revision: 68154
application can use ecore extn socket easyily
by using elm_window_add with ELM_WIN_SOCKET_IMAGE style.
And new widget Elm plug is similar with Elm image.
it can show socket's image using connect API.
I add test code also(test_win_socket/plug).
SVN revision: 67245
Wayland Engine. Give elm window some 'framespace' and borders for
wayland_shm.
NB: This means that you can now build & run elm apps for Wayland :)
SVN revision: 66767
win_resize_object_add(win, subobj);
object_content_set(otherobj, subobj);
object_del(win);
ERR<21326>:elm-externals elm_widget.c:978 elm_widget_sub_object_del() removing sub object 0xdeadbeef (some_stupid_widget) from parent 0xRRRRRRRR (win), but elm-parent is different 0xFUCKTHIS (NOT EVEN A WIDGET)!
SVN revision: 65884
elm_win.c: In function ‘elm_win_focus_get’:
elm_win.c:2182:4: warning: ‘return’ with no value, in function returning non-void
Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
SVN revision: 65527
This reverts commit 64549.
I gotta adimt, your commit looks correct to me, but hey, it breaks
elementary_test's "Window Inline" test... Please investigate it further
and make re-apply your commit afetr your solve these issues.
SVN revision: 64605
currently, only X window system undergo async problem,
but other windowing system meet same problem if it have asyncmode.
so I dont have to handle per-display specifics higher up above ecore-evas.
(use ecore_evas_request_XXX instead of ecore_evas_x11_request_XXX)
not only async windowing system but also situation wm refuse resizing request,
make request size != current size.
so I'll implement ee->req value to other windowing system.
--under this line, and those below, will be ignored--
M elm_win.c
SVN revision: 64549
First things first, I'm not sure I'm setting the right variable on
the setlocale() call, so someone more knowledgeable can look at it and fix it.
How this works, you say? Just like elm_object_text_part_set(), except now it
will pass the string given through dgettext() with the given domain (NULL
means it uses whatever the app set with textdomain()), and when changing
language with elm_language_set(), it will re-set the strings with a new
translation.
SVN revision: 64179
This contains a very simple and stupid window manager to be used in
FB, PS3 or similar single-window engines. Everybody is welcome to
improve it, particularly:
* Edje: better border decoration theme
* Edje: nice background
* C + Edje: taskbar with minimized items.
* C + Edje: find a better protocol to determine window size,
accounting border decoration without account shadow! Right now I'm
taking everything :-P
* C: window management keys (Alt+F4 and like)
How to use: export ELM_ENGINE=ews
How to configure backing store: export ECORE_EVAS_EWS=engine❌y:w:h:options
Example:
{{{
export ECORE_EVAS_EWS=software_x11:0:0:1024:768
export ELM_ENGINE=ews
elementary_test
}}}
Bugs: maybe many, but so far seems it wouldn't take mouse events for
secondary windows. Will check it later.
SVN revision: 63849
Hi All,
If ecore_evas_[not_software_x11]_new(); returns NULL while elm_win_add(); is
called,
then ecore_evas_software_x11_new(); is used instead of other engines.
(FALLBACK_TRY)
But the configuration value for engine is not changed. This makes improper
result.
After FALLBACK_TRY, the elm_win works with different configuration value.
In this case, win->xwin (_elm_win_xwindow_get()) gives NULL.
and elm_win_xsinodow_get() returns 0 also.
Please refer to attached patch. Thanks a lot
Sincerely,
Shinwoo Kim.
SVN revision: 61894
This engine just creates a buffer and renders everything to that buffer.
It's really useful for creating emulations of input/output and taking
window captures from them.
SVN revision: 61688
Subject: [E-devel] [patch] elm_win - add continuous capturing screen
I've made a patch about elm_win.
Adding repeat option to support continuous capturing the screen.
Repeat range is can set from 1 to 999.
Filename is set like "filename001.png"
SVN revision: 61034