[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Resurrecting the KoRepaintManager
From:       Thomas Zander <zander () kde ! org>
Date:       2007-10-31 9:48:47
Message-ID: 200710311048.47354.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 30 October 2007 22:12:04 Johannes Simon wrote:
> Am Dienstag, den 30.10.2007, 17:05 +0100 schrieb Thomas Zander:
> > But I still think you should
> > look at the repaintManager since those ideas at one point have been coded
> > into that some time ago :)
>
> Ok, I looked at your original implementation from a while ago, and a
> bunch of questions arose immediately. I'd be glad if you could give a
> couple of comments on what you meant to do with the code ;)
>
> Number one: Why can a KoRepaintManager contain other KoRMs? If they are
> connected to a KoCanvasBase, I don't see a reason for it to contain
> other repaintManagers that also contain a canvas. Also, why are they
> bound to a KoSelection?

Thats stuff that actually got moved to the KoShapeManager, so there is no need 
for that anymore.
You just need to somehow get a notification from the ShapeManager that a 
particular shape called a repaint on itself so you can invalidate the pixmap 
for it.

> I am willing to reuse your existing code and ideas, but not before I
> understand them ;)

Fair enough ;)
You don't have to resurrect the class itself, just make sure that you get the 
ideas behind it so you don't have to retrace my steps.

Have fun! :)
-- 
Thomas Zander

["signature.asc" (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]