[PATCH] elementary_test:clock couldn't be maxmised

juan.j.zhao at linux.intel.com juan.j.zhao at linux.intel.com
Fri Jul 6 03:26:41 PDT 2012


From: Juan Zhao <juan.j.zhao at linux.intel.com>

On wayland, elementary_test couldn't be maximised.
It's because of the clock window's weight is 0.
We should set its weight in the application side.
---
 trunk/elementary/src/bin/test_clock.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/trunk/elementary/src/bin/test_clock.c b/trunk/elementary/src/bin/test_clock.c
index 6e28d21..ebbc096 100644
--- a/trunk/elementary/src/bin/test_clock.c
+++ b/trunk/elementary/src/bin/test_clock.c
@@ -111,6 +111,7 @@ test_clock(void *data __UNUSED__, Evas_Object *obj __UNUSED__, void *event_info
 
    bx = elm_box_add(win);
    elm_win_resize_object_add(win, bx);
+   evas_object_size_hint_weight_set(bx, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
    api->box = bx;
    evas_object_show(bx);
 
-- 
1.7.5.4



More information about the wayland-devel mailing list