From: Glenn Watson <glenn.watson@nokia.com>
Date: Tue, 26 Jun 2012 23:36:13 +0000 (+1000)
Subject: Fix performance issue with BorderImage element.
X-Git-Tag: upstream/5.2.1~1568
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a2aa4705702256c15aaaf64e08b90c4749233f9d;p=platform%2Fupstream%2Fqtdeclarative.git

Fix performance issue with BorderImage element.

When a small source image is used in repeat mode, a large number of
vertices and indices can be generated by the current algorithm.
Change the geometry hint to static data, so the renderer plugin will
store the data in a VBO in GPU memory.

Task-number: QTBUG-21728
Change-Id: I07b3172eef8569bec2f4acebfb7965625bb5e63b
Reviewed-by: Michael Brasser <michael.brasser@nokia.com>
---

diff --git a/src/quick/items/qquickninepatchnode.cpp b/src/quick/items/qquickninepatchnode.cpp
index 649fa52..d304e2d 100644
--- a/src/quick/items/qquickninepatchnode.cpp
+++ b/src/quick/items/qquickninepatchnode.cpp
@@ -50,6 +50,9 @@ QQuickNinePatchNode::QQuickNinePatchNode()
     , m_dirtyGeometry(false)
     , m_mirror(false)
 {
+    m_geometry.setIndexDataPattern(QSGGeometry::StaticPattern);
+    m_geometry.setVertexDataPattern(QSGGeometry::StaticPattern);
+
     setOpaqueMaterial(&m_material);
     setMaterial(&m_materialO);
     setGeometry(&m_geometry);