Mipmapping concept problem

[Dmitry Kazakov]

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
> 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.
>

Then how should we paint KisPaintDevice onto QPainter?

PS:
/me's guts don't really like the perspective of writing their own
smooth-scaling code :)

-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20100603/bf6bfd61/attachment.htm