Hi Jorge! On Thu, Jul 26, 2012 at 6:09 PM, Jorge Pereira <jperei...@gmail.com> wrote: > > I'm having problem when call RenderTo() after loading images > with 16mb or larger, > in my mind could've some solution for when has big images, can limit > the maximum size > for used surface. (ok, i know that quality of image will be affected)
Care to give us some more information? * Image format: jpeg, png, gif? * What kind of problems? Or are you just running out of memory. When asking for help it's usually better if you could send a small code example that reproduces your problem so we can see exactly what you mean, and attach the problematic image. > > we are doing a module for handler "thumbnails" that sometime the > images can be so > larger like 16Mb pixels. my environment is a embedded system with > limited resources! Well, many (if not most) DFB users have same scenario so this should be interesting to all of us. FWIW, I've had a perhaps similar problem when I want to run some DirectFB code that I consider dangerous or unstable. For instance, an image viewer implementation where the image provided by user and therefore can't be trusted. Our solution was to simply put that code on a separate program (if you have another layer) and then call this program from our main app. If this child process dies for some reason; we can simply catch the issue and recover gracefully :-) It's a "sandbox" solution. FWIW (2) , I mantain a Lua binding for DirectFB. Since Lua it's very easy, I find it really useful for testing and quick try apps. https://github.com/ezequielgarcia/directfb-lua Hope this helps, Ezequiel. _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev