2011-06-03 00:09:25 -07:00
|
|
|
#include <Elementary.h>
|
|
|
|
#include "elm_priv.h"
|
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
static const char GLVIEW_SMART_NAME[] = "elm_glview";
|
|
|
|
|
|
|
|
#define ELM_GLVIEW_DATA_GET(o, sd) \
|
|
|
|
Elm_Glview_Smart_Data * sd = evas_object_smart_data_get(o)
|
|
|
|
|
|
|
|
#define ELM_GLVIEW_DATA_GET_OR_RETURN(o, ptr) \
|
|
|
|
ELM_GLVIEW_DATA_GET(o, ptr); \
|
|
|
|
if (!ptr) \
|
|
|
|
{ \
|
|
|
|
CRITICAL("No widget data for object %p (%s)", \
|
|
|
|
o, evas_object_type_get(o)); \
|
|
|
|
return; \
|
|
|
|
}
|
|
|
|
|
|
|
|
#define ELM_GLVIEW_DATA_GET_OR_RETURN_VAL(o, ptr, val) \
|
|
|
|
ELM_GLVIEW_DATA_GET(o, ptr); \
|
|
|
|
if (!ptr) \
|
|
|
|
{ \
|
|
|
|
CRITICAL("No widget data for object %p (%s)", \
|
|
|
|
o, evas_object_type_get(o)); \
|
|
|
|
return val; \
|
|
|
|
}
|
|
|
|
|
|
|
|
#define ELM_GLVIEW_CHECK(obj) \
|
|
|
|
if (!obj || !elm_widget_type_check((obj), GLVIEW_SMART_NAME, __func__)) \
|
|
|
|
return
|
|
|
|
|
|
|
|
typedef struct _Elm_Glview_Smart_Data Elm_Glview_Smart_Data;
|
|
|
|
|
|
|
|
struct _Elm_Glview_Smart_Data
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
Elm_Widget_Smart_Data base; /* base widget smart data as
|
|
|
|
* first member obligatory, as
|
|
|
|
* we're inheriting from it */
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Elm_GLView_Mode mode;
|
|
|
|
Elm_GLView_Resize_Policy scale_policy;
|
|
|
|
Elm_GLView_Render_Policy render_policy;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Evas_GL *evasgl;
|
|
|
|
Evas_GL_Config *config;
|
|
|
|
Evas_GL_Surface *surface;
|
|
|
|
Evas_GL_Context *context;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Evas_Coord w, h;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Elm_GLView_Func_Cb init_func;
|
|
|
|
Elm_GLView_Func_Cb del_func;
|
|
|
|
Elm_GLView_Func_Cb resize_func;
|
|
|
|
Elm_GLView_Func_Cb render_func;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Ecore_Idle_Enterer *render_idle_enterer;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
Eina_Bool initialized : 1;
|
|
|
|
Eina_Bool resized : 1;
|
2011-06-03 00:09:25 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
static const char SIG_FOCUSED[] = "focused";
|
|
|
|
static const char SIG_UNFOCUSED[] = "unfocused";
|
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
/* smart callbacks coming from elm glview objects: */
|
|
|
|
static const Evas_Smart_Cb_Description _smart_callbacks[] = {
|
|
|
|
{SIG_FOCUSED, ""},
|
|
|
|
{SIG_UNFOCUSED, ""},
|
|
|
|
{NULL, NULL}
|
|
|
|
};
|
2012-05-02 18:19:05 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
EVAS_SMART_SUBCLASS_NEW
|
|
|
|
(GLVIEW_SMART_NAME, _elm_glview, Elm_Widget_Smart_Class,
|
|
|
|
Elm_Widget_Smart_Class, elm_widget_smart_class_get, _smart_callbacks);
|
2012-05-02 18:19:05 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
static Eina_Bool
|
|
|
|
_elm_glview_smart_on_focus(Evas_Object *obj)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
if (elm_widget_focus_get(obj))
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_focus_set(ELM_WIDGET_DATA(sd)->resize_obj, EINA_TRUE);
|
2011-06-03 00:09:25 -07:00
|
|
|
evas_object_smart_callback_call(obj, SIG_FOCUSED, NULL);
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_focus_set(ELM_WIDGET_DATA(sd)->resize_obj, EINA_FALSE);
|
2011-06-03 00:09:25 -07:00
|
|
|
evas_object_smart_callback_call(obj, SIG_UNFOCUSED, NULL);
|
|
|
|
}
|
2012-05-03 15:43:42 -07:00
|
|
|
|
|
|
|
return EINA_TRUE;
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
_glview_update_surface(Evas_Object *obj)
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
|
|
|
if (!sd) return;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->surface)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_image_native_surface_set
|
|
|
|
(ELM_WIDGET_DATA(sd)->resize_obj, NULL);
|
|
|
|
evas_gl_surface_destroy(sd->evasgl, sd->surface);
|
|
|
|
sd->surface = NULL;
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_image_size_set(ELM_WIDGET_DATA(sd)->resize_obj, sd->w, sd->h);
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (!sd->surface)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
|
|
|
Evas_Native_Surface ns;
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->surface = evas_gl_surface_create
|
|
|
|
(sd->evasgl, sd->config, sd->w, sd->h);
|
|
|
|
evas_gl_native_surface_get(sd->evasgl, sd->surface, &ns);
|
|
|
|
evas_object_image_native_surface_set
|
|
|
|
(ELM_WIDGET_DATA(sd)->resize_obj, &ns);
|
2011-06-03 00:09:25 -07:00
|
|
|
elm_glview_changed_set(obj);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
2012-05-03 15:43:42 -07:00
|
|
|
_elm_glview_smart_resize(Evas_Object *obj,
|
|
|
|
Evas_Coord w,
|
|
|
|
Evas_Coord h)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
_elm_glview_parent_sc->base.resize(obj, w, h);
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->resized = EINA_TRUE;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->scale_policy == ELM_GLVIEW_RESIZE_POLICY_RECREATE)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
|
|
|
if ((w == 0) || (h == 0))
|
|
|
|
{
|
|
|
|
w = 64;
|
|
|
|
h = 64;
|
|
|
|
}
|
2012-05-03 15:43:42 -07:00
|
|
|
|
|
|
|
if ((sd->w == w) && (sd->h == h)) return;
|
|
|
|
|
|
|
|
sd->w = w;
|
|
|
|
sd->h = h;
|
|
|
|
|
|
|
|
_glview_update_surface(obj);
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-06-03 10:44:24 -07:00
|
|
|
static Eina_Bool
|
2011-06-03 00:09:25 -07:00
|
|
|
_render_cb(void *obj)
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
// Do a make current
|
2012-05-03 15:43:42 -07:00
|
|
|
if (!evas_gl_make_current(sd->evasgl, sd->surface, sd->context))
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->render_idle_enterer = NULL;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
ERR("Failed doing make current.\n");
|
2011-06-03 00:09:25 -07:00
|
|
|
return EINA_FALSE;
|
|
|
|
}
|
|
|
|
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
// Call the init function if it hasn't been called already
|
2012-05-03 15:43:42 -07:00
|
|
|
if (!sd->initialized)
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->init_func) sd->init_func(obj);
|
|
|
|
sd->initialized = EINA_TRUE;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
}
|
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->resized)
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->resize_func) sd->resize_func(obj);
|
|
|
|
sd->resized = EINA_FALSE;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
}
|
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
// Call the render function
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->render_func) sd->render_func(obj);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
// Depending on the policy return true or false
|
2012-05-03 15:43:42 -07:00
|
|
|
if (sd->render_policy == ELM_GLVIEW_RENDER_POLICY_ON_DEMAND)
|
2011-06-03 10:58:08 -07:00
|
|
|
return EINA_TRUE;
|
2012-05-03 15:43:42 -07:00
|
|
|
else if (sd->render_policy == ELM_GLVIEW_RENDER_POLICY_ALWAYS)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
|
|
|
// Return false so it only runs once
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->render_idle_enterer = NULL;
|
2011-06-03 00:09:25 -07:00
|
|
|
return EINA_FALSE;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
ERR("Invalid Render Policy.\n");
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->render_idle_enterer = NULL;
|
2011-06-03 00:09:25 -07:00
|
|
|
return EINA_FALSE;
|
|
|
|
}
|
2012-05-03 15:43:42 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
return EINA_TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
_set_render_policy_callback(Evas_Object *obj)
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
switch (sd->render_policy)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
|
|
|
case ELM_GLVIEW_RENDER_POLICY_ON_DEMAND:
|
2012-05-03 15:43:42 -07:00
|
|
|
// Delete idle_enterer if it for some reason is around
|
|
|
|
if (sd->render_idle_enterer)
|
|
|
|
{
|
|
|
|
ecore_idle_enterer_del(sd->render_idle_enterer);
|
|
|
|
sd->render_idle_enterer = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Set pixel getter callback
|
|
|
|
evas_object_image_pixels_get_callback_set
|
|
|
|
(ELM_WIDGET_DATA(sd)->resize_obj,
|
|
|
|
(Evas_Object_Image_Pixels_Get_Cb)_render_cb,
|
|
|
|
obj);
|
|
|
|
break;
|
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
case ELM_GLVIEW_RENDER_POLICY_ALWAYS:
|
2012-05-03 15:43:42 -07:00
|
|
|
// Unset the pixel getter callback if set already
|
|
|
|
evas_object_image_pixels_get_callback_set
|
|
|
|
(ELM_WIDGET_DATA(sd)->resize_obj, NULL, NULL);
|
|
|
|
|
|
|
|
break;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
default:
|
2012-05-03 15:43:42 -07:00
|
|
|
ERR("Invalid Render Policy.\n");
|
|
|
|
return;
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
static void
|
|
|
|
_elm_glview_smart_add(Evas_Object *obj)
|
|
|
|
{
|
|
|
|
EVAS_SMART_DATA_ALLOC(obj, Elm_Glview_Smart_Data);
|
|
|
|
|
|
|
|
// Create image to render Evas_GL Surface
|
|
|
|
ELM_WIDGET_DATA(priv)->resize_obj =
|
|
|
|
evas_object_image_filled_add(evas_object_evas_get(obj));
|
|
|
|
evas_object_image_size_set(ELM_WIDGET_DATA(priv)->resize_obj, 1, 1);
|
|
|
|
|
|
|
|
_elm_glview_parent_sc->base.add(obj);
|
2012-07-17 11:44:43 -07:00
|
|
|
|
|
|
|
// Evas_GL
|
|
|
|
priv->evasgl = evas_gl_new(evas_object_evas_get(obj));
|
|
|
|
if (!priv->evasgl)
|
|
|
|
{
|
|
|
|
ERR("Failed Creating an Evas GL Object.\n");
|
|
|
|
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Create a default config
|
|
|
|
priv->config = evas_gl_config_new();
|
|
|
|
if (!priv->config)
|
|
|
|
{
|
|
|
|
ERR("Failed Creating a Config Object.\n");
|
|
|
|
evas_object_del(obj);
|
|
|
|
|
|
|
|
evas_gl_free(priv->evasgl);
|
|
|
|
priv->evasgl = NULL;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
priv->config->color_format = EVAS_GL_RGB_888;
|
|
|
|
|
|
|
|
// Initialize variables
|
|
|
|
priv->mode = 0;
|
|
|
|
priv->scale_policy = ELM_GLVIEW_RESIZE_POLICY_RECREATE;
|
|
|
|
priv->render_policy = ELM_GLVIEW_RENDER_POLICY_ON_DEMAND;
|
|
|
|
priv->surface = NULL;
|
|
|
|
|
|
|
|
// Initialize it to (64,64) (It's an arbitrary value)
|
|
|
|
priv->w = 64;
|
|
|
|
priv->h = 64;
|
|
|
|
|
|
|
|
// Initialize the rest of the values
|
|
|
|
priv->init_func = NULL;
|
|
|
|
priv->del_func = NULL;
|
|
|
|
priv->render_func = NULL;
|
|
|
|
priv->render_idle_enterer = NULL;
|
|
|
|
priv->initialized = EINA_FALSE;
|
|
|
|
priv->resized = EINA_FALSE;
|
|
|
|
|
|
|
|
// Create Context
|
|
|
|
priv->context = evas_gl_context_create(priv->evasgl, NULL);
|
|
|
|
if (!priv->context)
|
|
|
|
{
|
|
|
|
ERR("Error Creating an Evas_GL Context.\n");
|
|
|
|
evas_object_del(obj);
|
|
|
|
|
|
|
|
evas_gl_config_free(priv->config);
|
|
|
|
evas_gl_free(priv->evasgl);
|
|
|
|
priv->evasgl = NULL;
|
|
|
|
return;
|
|
|
|
}
|
2012-05-03 15:43:42 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
_elm_glview_smart_del(Evas_Object *obj)
|
|
|
|
{
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
|
|
|
|
|
|
|
// Call delete func if it's registered
|
|
|
|
if (sd->del_func)
|
|
|
|
{
|
|
|
|
evas_gl_make_current(sd->evasgl, sd->surface, sd->context);
|
|
|
|
sd->del_func(obj);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (sd->render_idle_enterer) ecore_idle_enterer_del(sd->render_idle_enterer);
|
|
|
|
|
|
|
|
if (sd->surface) evas_gl_surface_destroy(sd->evasgl, sd->surface);
|
|
|
|
if (sd->context) evas_gl_context_destroy(sd->evasgl, sd->context);
|
|
|
|
if (sd->config) evas_gl_config_free(sd->config);
|
|
|
|
if (sd->evasgl) evas_gl_free(sd->evasgl);
|
|
|
|
|
|
|
|
_elm_glview_parent_sc->base.del(obj); /* handles freeing sd */
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
_elm_glview_smart_set_user(Elm_Widget_Smart_Class *sc)
|
|
|
|
{
|
|
|
|
sc->base.add = _elm_glview_smart_add;
|
|
|
|
sc->base.del = _elm_glview_smart_del;
|
|
|
|
sc->base.resize = _elm_glview_smart_resize;
|
|
|
|
|
|
|
|
sc->on_focus = _elm_glview_smart_on_focus;
|
|
|
|
}
|
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
EAPI Evas_Object *
|
|
|
|
elm_glview_add(Evas_Object *parent)
|
|
|
|
{
|
2012-05-02 18:19:05 -07:00
|
|
|
Evas *e;
|
2012-05-03 15:43:42 -07:00
|
|
|
Evas_Object *obj;
|
|
|
|
|
|
|
|
EINA_SAFETY_ON_NULL_RETURN_VAL(parent, NULL);
|
|
|
|
|
|
|
|
e = evas_object_evas_get(parent);
|
|
|
|
if (!e) return NULL;
|
2012-05-02 10:00:56 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
obj = evas_object_smart_add(e, _elm_glview_smart_class_new());
|
2012-05-02 10:00:56 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
|
|
|
if (!sd->evasgl)
|
2012-07-17 11:44:43 -07:00
|
|
|
return NULL;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-07-17 11:44:43 -07:00
|
|
|
if (!elm_widget_sub_object_add(parent, obj))
|
|
|
|
ERR("could not add %p as sub object of %p", obj, parent);
|
2012-05-03 15:43:42 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
return obj;
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI Evas_GL_API *
|
2011-06-03 10:48:45 -07:00
|
|
|
elm_glview_gl_api_get(const Evas_Object *obj)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj) NULL;
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
return evas_gl_api_get(sd->evasgl);
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
EAPI Eina_Bool
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_mode_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Mode mode)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj) EINA_FALSE;
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
// Set the configs
|
2012-05-03 15:43:42 -07:00
|
|
|
if (mode & ELM_GLVIEW_ALPHA) sd->config->color_format = EVAS_GL_RGBA_8888;
|
|
|
|
else sd->config->color_format = EVAS_GL_RGB_888;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (mode & ELM_GLVIEW_DEPTH) sd->config->depth_bits = EVAS_GL_DEPTH_BIT_24;
|
|
|
|
else sd->config->depth_bits = EVAS_GL_DEPTH_NONE;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
if (mode & ELM_GLVIEW_STENCIL)
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->config->stencil_bits = EVAS_GL_STENCIL_BIT_8;
|
|
|
|
else sd->config->stencil_bits = EVAS_GL_STENCIL_NONE;
|
2012-01-12 06:35:43 -08:00
|
|
|
|
|
|
|
if (mode & ELM_GLVIEW_DIRECT)
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->config->options_bits = EVAS_GL_OPTIONS_DIRECT;
|
|
|
|
else sd->config->options_bits = EVAS_GL_OPTIONS_NONE;
|
2011-06-03 00:09:25 -07:00
|
|
|
|
|
|
|
// Check for Alpha Channel and enable it
|
|
|
|
if (mode & ELM_GLVIEW_ALPHA)
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_image_alpha_set(ELM_WIDGET_DATA(sd)->resize_obj, EINA_TRUE);
|
2011-06-03 10:44:24 -07:00
|
|
|
else
|
2012-05-03 15:43:42 -07:00
|
|
|
evas_object_image_alpha_set(ELM_WIDGET_DATA(sd)->resize_obj, EINA_FALSE);
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->mode = mode;
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
elm_glview_changed_set(obj);
|
|
|
|
|
|
|
|
return EINA_TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI Eina_Bool
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_resize_policy_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Resize_Policy policy)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj) EINA_FALSE;
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (policy == sd->scale_policy) return EINA_TRUE;
|
2011-06-03 00:09:25 -07:00
|
|
|
switch (policy)
|
|
|
|
{
|
|
|
|
case ELM_GLVIEW_RESIZE_POLICY_RECREATE:
|
|
|
|
case ELM_GLVIEW_RESIZE_POLICY_SCALE:
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->scale_policy = policy;
|
|
|
|
_glview_update_surface(obj);
|
|
|
|
elm_glview_changed_set(obj);
|
|
|
|
return EINA_TRUE;
|
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
default:
|
2012-05-03 15:43:42 -07:00
|
|
|
ERR("Invalid Scale Policy.\n");
|
|
|
|
return EINA_FALSE;
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI Eina_Bool
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_render_policy_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Render_Policy policy)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj) EINA_FALSE;
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2011-06-03 10:44:24 -07:00
|
|
|
if ((policy != ELM_GLVIEW_RENDER_POLICY_ON_DEMAND) &&
|
2011-06-03 00:09:25 -07:00
|
|
|
(policy != ELM_GLVIEW_RENDER_POLICY_ALWAYS))
|
|
|
|
{
|
|
|
|
ERR("Invalid Render Policy.\n");
|
|
|
|
return EINA_FALSE;
|
|
|
|
}
|
2012-05-03 15:43:42 -07:00
|
|
|
|
|
|
|
if (sd->render_policy == policy) return EINA_TRUE;
|
|
|
|
|
|
|
|
sd->render_policy = policy;
|
2011-06-03 00:09:25 -07:00
|
|
|
_set_render_policy_callback(obj);
|
|
|
|
_glview_update_surface(obj);
|
2012-05-03 15:43:42 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
return EINA_TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_size_set(Evas_Object *obj,
|
|
|
|
int w,
|
|
|
|
int h)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
|
|
|
|
|
|
|
if ((w == sd->w) && (h == sd->h)) return;
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->w = w;
|
|
|
|
sd->h = h;
|
2011-06-03 00:09:25 -07:00
|
|
|
_glview_update_surface(obj);
|
2012-05-03 15:43:42 -07:00
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
elm_glview_changed_set(obj);
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_size_get(const Evas_Object *obj,
|
|
|
|
int *w,
|
|
|
|
int *h)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 10:44:24 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
if (w) *w = sd->w;
|
|
|
|
if (h) *h = sd->h;
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|
|
|
|
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_init_func_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Func_Cb func)
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->initialized = EINA_FALSE;
|
|
|
|
sd->init_func = func;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_del_func_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Func_Cb func)
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->del_func = func;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_resize_func_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Func_Cb func)
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->resize_func = func;
|
Upon reviewing the elm_glview, I've realized a few issues and mistakes that i've
made originally so I've made some changes/ updates to elm_glview
1.) GL Resource Deletion in ELM_GLView
In order to delete GL resources, the current approach simply registered a
delete callback to the GLView object and handled resource deletion there.
Unfortunately, using the delete callback did not guarantee the glview context to be
current. In order to guarantee that the current context was the glview context,
the make_current call needs to be called explicitly. Since we were hiding all the
make current details in elm_glview, i've decided to add an API that registers a
delete callback function. I know that this may seem redundant since there is already
a delete callback that you can register with glview objects. Unfortunately, this is the
only option that we have apart from exposing make_current, which is something that
went again what we are trying to do with elm_glview.
Since adding delete callback alone seemed a little out of place, i've taken the liberty
to add other callback functions to make it seem consistent.
void elm_glview_init_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_del_func_set(Evas_Object *obj, Elm_GLView_Func func);
void elm_glview_resize_func_set(Evas_Object *obj, Elm_GLView_Func func);
resize callback can be controversial as well but I want to argue that adding this callback
makes the render function a lot cleaner. To handle resize differently, the user in
render function needs to manually compare and see if the size has changed, and
then handle the cases. Doing all of this internally once makes the developers life
a lot easier in my opinion.
these callback functions do make the render function a lot cleaner. You can check
out the updated test_glview.c or newly added test_glview_simple.
2.) Minor bug fixes/changes
elm_glview_scale_policy_set() was supposed to be elm_glview_resize_policy_set()
but it somehow evaded our reviews. That has been fixed.
Also, in _glview_resize, after updating the surface, it was explicitly calling the
render function. It is actually unnecessary here and calling it here will cause
problems if resize gets called before everything else is setup properly. So that has
been commented out.
3.) test_glview & test_glview_simple
elementary_test case for glview has been updated to reflect the api changes.
when you run the elmentary_test, you need to make sure that you set
ELM_ENGINE=gl as glview currently only runs on gl backend.
test_glview runs the gears example. For testing purposes I've included a simple
glview test case that renders a triangle and changing background color.
SVN revision: 60517
2011-06-20 03:55:02 -07:00
|
|
|
}
|
|
|
|
|
2011-06-03 00:09:25 -07:00
|
|
|
EAPI void
|
2012-05-03 15:43:42 -07:00
|
|
|
elm_glview_render_func_set(Evas_Object *obj,
|
|
|
|
Elm_GLView_Func_Cb func)
|
2011-06-03 00:09:25 -07:00
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
2011-06-03 00:09:25 -07:00
|
|
|
|
2012-05-03 15:43:42 -07:00
|
|
|
sd->render_func = func;
|
2011-06-03 00:09:25 -07:00
|
|
|
_set_render_policy_callback(obj);
|
|
|
|
}
|
|
|
|
|
|
|
|
EAPI void
|
|
|
|
elm_glview_changed_set(Evas_Object *obj)
|
|
|
|
{
|
2012-05-03 15:43:42 -07:00
|
|
|
ELM_GLVIEW_CHECK(obj);
|
|
|
|
ELM_GLVIEW_DATA_GET(obj, sd);
|
|
|
|
|
|
|
|
evas_object_image_pixels_dirty_set
|
|
|
|
(ELM_WIDGET_DATA(sd)->resize_obj, EINA_TRUE);
|
|
|
|
if (sd->render_policy == ELM_GLVIEW_RENDER_POLICY_ALWAYS &&
|
|
|
|
!sd->render_idle_enterer)
|
|
|
|
sd->render_idle_enterer =
|
|
|
|
ecore_idle_enterer_before_add((Ecore_Task_Cb)_render_cb, obj);
|
2011-06-03 00:09:25 -07:00
|
|
|
}
|