On Thu, Jun 26, 2008 at 9:23 AM, yahvuu <yahvuu@xxxxxxxxx> wrote: > Hi all, > > if i read gegl-operation-area-filter.c correctly, both the bounding box and the > invalidate_by_change region grow by the amount specified in prepare(). > Assuming all area operations are by type similar to blur, i had expected that > only the input region (required_for_output) grows. Are there other types of > area filters which require this behaviour? > > How are area filters supposed to handle the source node's bounding box? > For correctly handling border pixels, a filter probably has to differentiate > between the borders of the currently rendered tile and the borders of > the source's bounding box. The current blur implementations > don't handle this, is there a reference filter which does? There currently isn't any filters giving such a behavior. Making the blur filter assume the buffer abyss (the region outside the defined image) to be transparent and extend the defined region by the kernel radius gives what I expect as the result from blurring it, a rectangle with a fuzzy edge. All the information to deal with this in different ways should be available, I do not remember if any of the operations currently shipping with GEGL does so though. /Øyvind K. -- «The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ http://ffii.org/ _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
