Mipmapping concept problem
dimula73 at gmail.com
Thu Jun 3 09:21:10 CEST 2010
On Thu, Jun 3, 2010 at 11:04 AM, Boudewijn Rempt <> wrote:
> 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
> > fullsized QImage.
> No, no: that should never happen. The QImage in KisPrescaledProjection
> never be bigger than the view. The big QImage cache is a 100% projection of
> the KisImage's projection -- and that's not good.
Then how should we paint KisPaintDevice onto QPainter?
/me's guts don't really like the perspective of writing their own
smooth-scaling code :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kimageshop