Hi all,
When we have inlined windows, the alpha_set will apply to
win->img_obj. But on alpha_get it will query from win->ee, what's the
reasoning in it? Who did it (Raster?), could envision more leftovers?
Also, found "transparency" and since we had "alpha" and "shaped" I got
really confused. Looking at the code seems that one sets:
shaped: einfo->info.mask = ee->engine.x.mask;
transparent: einfo->info.destination_alpha = transparent;
alpha: einfo->info.destination_alpha = alpha; /* with couple of
additions before */
Then I wonder why keeping these confusing names? Most code I've seen
try alpha, then shaped and they don't even know about transparency.
Why not just make "ecore_evas_alpha_set()" and an auxiliary mode to
set possible attempts:
ecore_evas_alpha_mode_set(ee, mode):
mode is one of:
ECORE_EVAS_ALPHA_ARGB = 1
ECORE_EVAS_ALPHA_BITMASK_SHAPED = 2
ECORE_EVAS_ALPHA_SOMETHING_I_DONT_GET_WHAT_TRANSPARENCY_IS = 4
ECORE_EVAS_ALPHA_BEST_EFFORT = 7 /* all of above, default */
then we deprecate the existing apis and keep only these 2, extending
the enum as required.
--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: [email protected]
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
