Summary:
1/2 year ago we have removed the automatic generation of legacy
headers. In this go we also removed the installation of legacy eo beta
APIs, as they definitly should not be used. However, there is the legacy
systray API which does not depend directly on eo. Apps could use this
before due to specifying the BETA define, now they only can call the
API, but cannot construct the object they need. This adds this back
under the beta tag, so those apps can continue working.
I am not sure myself if i like the commit or not, its a beta thing, why
should we fix it. However, Its quite a easy thing to add such a
constructor method for us, and enables app to continue working.
Reviewers: zmike, segfaultxavi
Reviewed By: zmike
Subscribers: jf_simon, cedric, #reviewers, #committers
Tags: #efl
Differential Revision: https://phab.enlightenment.org/D9757
}
}
+EAPI Elm_Systray*
+elm_systray_add(Evas_Object *win)
+{
+ return efl_add(ELM_SYSTRAY_CLASS, win);
+}
+
+
#include "elm_systray_eo.c"
# ifndef EFL_NOLEGACY_API_SUPPORT
# include "elm_systray_eo.legacy.h"
# endif
+
+/**
+ * Add a new systray element
+ *
+ * @param parent The parent object
+ * @return A new systray object which will be displayed on a window manager that provides appindicator support.
+ *
+ * @ingroup Elm_Systray
+ */
+EAPI Elm_Systray *elm_systray_add(Evas_Object *win);
+
#endif