Just discovered an interesting issue with evas:
evas_object_clip_set(obj,obj) is all bad.
This one line fixes the problem (which is mostly a PEBKAC, but still).
--- src/lib/canvas/evas_clip.c 16 Nov 2006 03:20:24 - 1.26
+++ src/lib/canvas/evas_clip.c 12 Apr 2007 02:48:10 -
On 04/08/2007 23:39, Ravenlock wrote:
> Hello,
>
> Attached is a small patch which will add a check box to the config panel
> that manipulates the clientlist menu.
>
> Presently there is a way to limit the length of the caption of
> clientlist menu items. However if you do not wish to limit th
> > But the 'problem' goes deeper than that. Right now the
> > argb data itself (ie. the result of loading things given only
> > the file/key/load_opts combo) may be shared by several cached
> > engine images, ie. images which have the same file/key/load_opts
> > but could have different 'displays
On Wednesday 11 April 2007 09:41:22 [EMAIL PROTECTED] wrote:
> Cedric wrote:
> > > this is why there is a specific engine copy wrapping the image
> > > - the RGBA_Image just acts as a source of RGBA pixel data.
> > > the wrapping engine image colds a pointer to that plus engine
> > > specific
Cedric wrote:
> > this is why there is a specific engine copy wrapping the image
> > - the RGBA_Image just acts as a source of RGBA pixel data.
> > the wrapping engine image colds a pointer to that plus engine
> > specific data. the image is also looked up not just by filename
> > + key,
