On Sat, 17 Dec 2005 10:58:43 -0500 Jason Tackaberry <[EMAIL PROTECTED]> babbled:
> On Sun, 2005-12-18 at 00:19 +0900, Carsten Haitzler wrote:
> > but where does evas fit in there? evas has its own yuv (yv12) import
> > mechanism and eventually i want to merge all that down into the engine
> > leve
On Sun, 2005-12-18 at 00:19 +0900, Carsten Haitzler wrote:
> but where does evas fit in there? evas has its own yuv (yv12) import mechanism
> and eventually i want to merge all that down into the engine level so in
> theory
> it can hw accel if possible or simply sw convert - so you just provide y
On Sat, 17 Dec 2005 10:00:53 -0500 Jason Tackaberry <[EMAIL PROTECTED]> babbled:
> On Sat, 2005-12-17 at 18:27 +0900, Carsten Haitzler wrote:
> > technically - yes. it's a bug. it's due to the fact that the routines dont
> > have a special case for multiple when alpha doesnt contain sensible data
On Sat, 2005-12-17 at 18:27 +0900, Carsten Haitzler wrote:
> technically - yes. it's a bug. it's due to the fact that the routines dont
> have
> a special case for multiple when alpha doesnt contain sensible data (filling
> it
> in with an assumed 0xff) :)
I argued this on mplayer-dev, and provi
On Tue, 13 Dec 2005 23:45:40 -0500 Jason Tackaberry <[EMAIL PROTECTED]> babbled:
> I'm using an external library that generates a BGR32 image. The source
> image is only 24bpp, so the alpha channel is all zeroed. So, when I add
> the image to an evas canvas and use evas_object_image_data_set, I
I'm using an external library that generates a BGR32 image. The source
image is only 24bpp, so the alpha channel is all zeroed. So, when I add
the image to an evas canvas and use evas_object_image_data_set, I pass 0
to evas_object_image_alpha_set. My assumption is that this merely
indicates to E
