From: tasn <tasn@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Date: Mon, 31 Oct 2011 16:32:13 +0000 (+0000)
Subject: Elm test: Fixed label test's window size.
X-Git-Tag: REL_F_I9500_20120323_1~17^2~1434
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=67dc18d71a1ea1e1152b813f78746426a2ba26b2;p=framework%2Fuifw%2Felementary.git

Elm test: Fixed label test's window size.

This is actually a pretty important thing to remember.
elm_win_resize_object_add resizes the content to the size of the window,
the size of the window is only applied when the window is shown, at least on
the ecore evas. Is that wanted? or should we take the evas-object geometry
there? The problem I'm worried about is: writing beyond buffer limits.

git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/elementary@64579 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33
---

diff --git a/src/bin/test_label.c b/src/bin/test_label.c
index 46ea32f..d29b963 100644
--- a/src/bin/test_label.c
+++ b/src/bin/test_label.c
@@ -68,11 +68,10 @@ test_label(void *data __UNUSED__, Evas_Object *obj __UNUSED__, void *event_info
    elm_box_pack_end(bx, lb);
    evas_object_show(lb);
 
-   elm_win_resize_object_add(win, bx);
-   evas_object_show(bx);
-
    evas_object_resize(win, 320, 300);
 
+   evas_object_show(bx);
    evas_object_show(win);
+   elm_win_resize_object_add(win, bx);
 }
 #endif