2014-07-06 9:16 GMT+02:00 Diederik van Lierop <mail@...1689...>:
Hi ppl,
It's no surprise that filters can make Inkscape crawl, and I ran into that while digging into this bug
https://bugs.launchpad.net/inkscape/+bug/827192
In this case though, the area to be filtered measures 18416 x 17524 pixels, which is a bit too much for just on screen display. Is there any way to work around this? Can't we set an upper limit on the area, in order to keep Inkscape somewhat responsive? If it takes a few seconds that's OK IMHO in such extreme cases, but at least the user should be able to trust that Inkscape will recover.
The problem is that the dependent area of the filter effect in this case is extremely large, i.e. the Gaussian blur must be computed on this enormous surface in order for the result to be correct.
We could do three things a) put in some logic to arbitrarily stop rendering an effect when the dependent area crosses some threshold b) use stacked box blur instead of true Gaussian blur (though I doubt it would be faster) c) speed up the existing Gaussian blur implementation - it shouldn't be that slow
Regards, Krzysztof