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 objects. my
code to get the object above/below/on top and on bottom didn't look at the
delete_me flag and just gave u the object anyway. thus the object was still
there but flagged for deletion - thus u always got the same object handle. :)
fixed now in cvs. do a cvs update. :)
Had a guess it was something like that, though putting an evas_render in the loop didn't affect it at all earlier. Just tried it again with the new cvs code but still appears to fail. Didn't have much time to check it though, so it could have been an error on my part re-installing the libraries...will check more thoroughly tonight when I get back.
Cheers, Daniel.
-- email:[EMAIL PROTECTED] http://members.optusnet.com.au/stonierd/
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
