2012/8/17 Josh Andler <scislac@...400...>:
We still have some outstanding bugs with the new renderer which should really be addressed when possible. I know I will be going through the tracker soon to look for our blockers and must-fixes... others are welcome to do this as well.
The issues with the new renderer are as follows:
1. There are some rough edges caused by more SVG-compliant output (scaled strokes). More specifically, the selection cue no longer matches the visual bounding box of some objects.
2. The intermediate surfaces for pattern rendering are not computed correctly and the result is pixelation at high zoom levels. The relevant code is in sp-pattern.cpp lines 604-720 if someone wants to have a look.
3. Caching problems. In some instances, the caching mechanism does not invalidate everything it should. Sometimes it does not kep track of memory use properly and can take up several GB. There are some bug reports related to this. A related problem is that the cache is not preserved when objects are translated in the selector tool. Although this is only a missing optimization, it would substantially improve workflows involving blurred objects.
4. Cairo does not downscale bitmaps correctly. This is the worst issue, since it makes Inkscape useless when working with high resolution photos. The best solution is to implement mipmapping or at least better downscaling in Cairo. A temporary Inkscape-only solution would be to downscale the image to the correct size ourselves before outputting it to the screen.
Regards, Krzysztof