>> What do you do if such a native surface is set and one asks
>> for the argb data? What do you do about users setting native surfaces
>> which don't match with the display targets somehow (differing x
>> resources for example).
>> I'd say - restrict native surface api to only have a 'get'
>> func, ie. evas provides a suitable surface for you to draw to,
>> but not for you to 'set' one such...?
>>
>
> that would preclude evas ever being useful for a composite manager - as X
> itself provides you with the pixmap of the composited window. you don't have a
> choice there.
>
Ummm... Ok, but it would then seem as though this little piece
of native-surface image hell is going to be your fun and joy when
you get a chance sometime in the near future..? :)
PS.
I noticed you've been conspicuously quiet on the 'transforms/
filters' debate I've been putting poor Gustavo thru.. :) I'd do it
but not with arbitrary clipping, using transforms (or filters) and
masks instead. But maybe it's better if others give it a shot.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
