object inthe evas are in layers above the new one.. fix fix oops.. that was
a silly bug... :)
and well.. while i was at it.. some actual code in the render extension
support in the render engine in evas.. it onyl does image objects right
now.. and it doesnt do it very optimally.. consider that engine a work in
progres.. i'm finding what does and doesnt work well in the render extension
and noticing some holes in it... this one wont be ready any time soon
though... and the gl engine is still about 10 times faster on the same
hardware... and in theory both are hardware accelerated...
anyway only time will tell. the render extension doesnt do image
transforms.. so this wont help speed it up at all that much :(
SVN revision: 5267
so you cant look into them. all defines now become enums too - cleaner. no
more bypassing the api is possible :)
also added better checks and --with- stuff for imlib2, gl and ttf
SVN revision: 3548
it will render to a virtual image buffer just like it would to a window.
the logic works the exact same way as a window - it wil lonly render the rects
that changed. if a rect chnaged it expects that rect to have been cleared and
will blend the canvas ontop of the image - so you can use it to augment the
current image contents (though they will be permenantly modified). This is
specifically designed for doing things like rendering a canvas to be saved
to an image file.
WHEEEEEEEE :)
SVN revision: 3460
Carsten Haitzler