Because QtQuick is fine tuned to some specific use cases.
Because your code is not optimal.But when I use graphics view, updating items positions is so slow...
No, definitely not. That would break the whole architecture.I think using setPos() might be the culprit. Should I subclass QGraphicsSvgItem and use it's paint() to update it's position?
Bookmarks