Matthias Kleine wrote: > Matthias Kleine wrote: > >> I think it might be related to this bug report (5). The bug description >> does fit my code (itemChange is overridden in WayItem). > > removing itemChange did actually fix the bug I mentioned. So now I can > wrap my items in item groups. This doesn't help with my first problem, > though: Each time the position of the item group is changed, > boundingRect() is called on all its children due to a call of > fullUpdateHelper. That's exactly what I was trying to elide. > > I'm not sure were to go from here. Earlier on you suggested using > built-in graphic items, only. This isn't really an option for me, as it > would mean adding another layer of indirection (objects which manage > state of graphics items + actual graphics items) and would make the code > hardly more readable.
That was primarily to verify that the bottleneck is the java boundingRect() function. Are you new'ing QRectF's or are you caching them from call to call? > If I had some time I would try to implement some caching mechanism in Qt > itself, but I guess that has to wait for a while. If you still have any > other idea, please let me know. I'm out of ideas, sorry... As I said, it is a degenerate use-case ;( - Gunnar _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
