On Fri, 19 Feb 2010 21:24:57 +0300 Eugene Zagidullin <e.asphyx@xxxxxxxxx> wrote: > Yes, it's just what I mean. But this decomposition is a very > CPU-intensive operation. Is there a way to process whole image only > once, store output in a kind of cache and later update requested > region with cached data? Performing decomposition again and again > until whole image will be covered with ROIs and thus cached is waste > of time. I ran into the same problem with gegl:openraw-load. If get_bounding_box and importantly get_cached_region both return the entire image, then GEGL will submit one process request for the entire image and cache the result. I'm using this trick in a couple of ops currently, and while it doesn't appear to be explicitly documented anywhere, it always works. _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
