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

List:       kde-games-devel
Subject:    Re: [Kde-games-devel] Moving the KGameRenderer framework to
From:       Parker Coates <parker.coates () kdemail ! net>
Date:       2010-07-03 21:01:46
Message-ID: AANLkTinwH2Ijvtt-lIIcuk2UudCeyidFkAbMshr26hGe () mail ! gmail ! com
[Download RAW message or body]

On Sat, Jul 3, 2010 at 09:35, Stefan Majewsky wrote:
> On Thursday 01 July 2010 20:40:10 Miha Čančula wrote:
>> If I can make a suggestion (I'm late, I know...) I would export all
>> QGraphicsItem's properties, not only "frame". At least "pos" is useful for
>> animation and to avoid repeating code, as I see you had to add the
>> declaration in KDiamond as well.
>
> I did that this morging, but then I replaced the QObject/QGraphicsPixmapItem
> superclasses by QGraphicsObject (with a private QGraphicsPixmapItem child)
> after finally figuring out a way to get the input event routing right.

Does that mean that KGameRenderedItem no longer has a setOffset()
method? I use that in Killbots.

I'm also concerned with the potential runtime cost of doubling the
number of items in the scene. Would you mind elaborating on why you
felt the need to switch to QGraphicsObject? My understanding was that
it was only a convenience class for handling the QObject::parent()
QGraphicsItem::parent() conflict and the Q_INTERFACE.

Basically, I think "KGameRenderedItem is a QGraphicsPixmapItem" seems
a lot more natural than  "KGameRenderedItem has a
QGraphicsPixmapItem".

Parker
(Still out of town and slow to reply.)
_______________________________________________
kde-games-devel mailing list
kde-games-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-games-devel

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