Mipmapping concept problem

Boudewijn Rempt boud at valdyas.org
Thu Jun 3 09:04:05 CEST 2010

On Wednesday 02 June 2010, Dmitry Kazakov wrote:
> Hi, All!
> I was thinking over advantages/disadvantages of switching to
> KisImagePyramid projection backend and i'm in a trouble now:
> We wanted to switch to it for eliminating creation of a big QImage for
> caching the projection. But how will we paint KisPaintDevice onto
> KisPrescaledProjection's internal QImage? Current implementation creates
> temporary QImage and paints it onto prescaled projection with
> QPainter::draw. The problem is, when we zoom in/out we will create the same
> fullsized QImage.

No, no: that should never happen. The QImage in KisPrescaledProjection should 
never be bigger than the view. The big QImage cache is a 100% projection of 
the KisImage's projection -- and that's not good.

> That is, of course, not good. And i don't know how to
> solve this. Split the patch image into smaller ones? Or there is some other
> idea?

Boudewijn Rempt | http://www.valdyas.org

More information about the kimageshop mailing list