Hello, EFL developers.
I just have one question and need your opinions.
In many cases, many non-smart objects are used in elementary
e.g) evas_object_rectangle.
Those objects are passed to elm_widget APIs frequently which
calls the smart_object_data_get in API_ENTRY define.
Since those are not smart objects, they will be handled by
MAGIC_CHECK(EVAS_OBJ_SMART) in evas.
If EVAS_DEBUG_ABORT is enabled, in that case the program will be
aborted.
Consequently, elementary can't use the EVAS_DEBUG_ABORT property
usefully now as you can check it with elementary_test
So, my question is where do we fix this problem ?
1. Find all the non-smart objects in elementary then change to
smart objects?
2. Or before call the smart_object_data_get in API_ENTRY, check
the object_type then pass the API call if the objects are
non-smart?
3. Or skip the smart object MAGIC_CHECK in Evas?
4. Or leave them and don't use EVAS_DEBUG_ABORT?
What do you think about this?
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
