From 2264f3e2e9f59952761dbbcc7f9cf39333ea4488 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Iv=C3=A1n=20Briano?= Date: Tue, 2 Aug 2011 16:44:41 +0000 Subject: [PATCH] And it turns out this doesn't work that way, my bad. SVN revision: 62013 --- legacy/elementary/src/lib/Elementary.h.in | 7 ------- 1 file changed, 7 deletions(-) diff --git a/legacy/elementary/src/lib/Elementary.h.in b/legacy/elementary/src/lib/Elementary.h.in index 30efa08578..19116c6cab 100644 --- a/legacy/elementary/src/lib/Elementary.h.in +++ b/legacy/elementary/src/lib/Elementary.h.in @@ -1782,13 +1782,6 @@ extern "C" { * #ELM_WIN_INLINED_IMAGE, which needs a parent to retrieve the canvas on * which the image object will be created. * - * For any other type, if @p parent is @c NULL, then the window created - * will be independent of any other window in the application. When another - * widget is used as the @p parent, the window will visually be the same - * as any other, but it would be added as a sub-object of the given parent, - * which means that if the parent object is destroyed the window will also - * be destroyed. - * * @return The created object, or NULL on failure */ EAPI Evas_Object *elm_win_add(Evas_Object *parent, const char *name, Elm_Win_Type type);