aaah oops - thanks! thats a bug on my part. let me explain. in order for
evas to
"keep state" objects arent actually deleted when you call
evas_object_del. they
are "flagged for deletion" but left there, they will be deleted next
evas_render() cycle when it no longer needs the state for deleted
On Mon, 15 Mar 2004 10:53:21 -0300 Brizuela Ezequiel Hector
<[EMAIL PROTECTED]> babbled:
> I'm in list, but i'm not contributing (in a code way) with the proyect, but
> I trying to get updated with the "news" from the core of the proyect, so, as
> I can see as far, the problem is th
On Mon, 15 Mar 2004 20:36:31 + ESR <[EMAIL PROTECTED]> babbled:
> Howdy Y'all,
>
> Heres a little patch against e16/epplets/E-MemWatch.c to make it work
> properly with 2.6 Kernels.
in cvs :)
> elemental0125
>
> --- E-MemWatch.c.~1.15.~ Wed Jan 5 16:2
On Tue, 16 Mar 2004 04:13:08 +1000 Daniel Stonier <[EMAIL PROTECTED]>
babbled:
>
> >
> > ie
> > while ((o = evas_object_bottom_get(evas)) evas_object_del(o);
> >
> > will completely clear all objects in a canvas and empty it out
> > completely.
> >
>
>
Howdy Y'all,
Heres a little patch against e16/epplets/E-MemWatch.c to make it work
properly with 2.6 Kernels.
elemental0125
--- E-MemWatch.c.~1.15.~Wed Jan 5 16:24:00 2000
+++ E-MemWatch.cMon Mar 15 20:12:29 2004
@@ -48,6 +48,7 @@
Epplet_gadget close_button, mem_bar, swap_bar,
ie
while ((o = evas_object_bottom_get(evas)) evas_object_del(o);
will completely clear all objects in a canvas and empty it out
completely.
Had some problems with implementing this - have attached a simple test
program to illustrate the problem. At the first call of the
evas_object_bo
Title: RE: [E-devel] Build setup/Code testing - What can I do?
I'm in list, but i'm not contributing (in a code way) with the proyect, but I trying to get updated with the "news" from the core of the proyect, so, as I can see as far, the problem is that don't have a public.. mm.. how to tell i
What follows is the first in a series of patches
designed to speed up some of Evas' drawing/blending
C functions in the "engines/common" dir.
As later patches will involve non-trivial changes,
this first *very small* one is merely to fix a minor oversight
and add a trivial check i
