#ifdef INFINITE_CANVAS

[LukasT.dev@gmail.com]

On Thursday 10 December 2009 23:29:15 Dmitry Kazakov wrote:
> On Fri, Dec 11, 2009 at 1:17 AM, LukasT.dev at gmail.com
> 
> <lukast.dev at gmail.com>wrote:
> > On Thursday 10 December 2009 11:05:57 Dmitry Kazakov wrote:
> > > 1) Is there any link to read about INDEPENDENT_CANVAS?
> >
> > I give you the idea of what I have done. I added private member QImage
> > m_img
> > to KisQPainterCanvas and when the paint event is called with changed
> > rect, the
> > rect is painted to the QImage and then the rect is updated with other
> > QPainter
> > which is widget's one.
> >
> > > 2) Well, is there any way to move painting decorations and overlay
> >
> > outside
> >
> > > of paint event? We could prepare your QImage outside paint event, and
> >
> > just
> >
> > > copy it to the widget inside paintEvent? Is this possible?
> >
> > So we would not store one global QImage but allocate small ones per
> > paint- overlay action?
> 
> Hmm.. no. One global QImage. It is updated on the change of decorations.
> Inside paintEvent we just call gc.drawImage(qimage) and no updates. Is it
> possible? And will help to improve perfomance?
> 

If we are going to store the QImage as we do now, I don't see any speed ups. 
We are painting rectangles to QImage and then to underlaying system so I don't 
expect big speed improvement. When I added the QImage through the beta testing 
period, no one reported performance slowdown.