summaryrefslogtreecommitdiffstats
path: root/doc/src/frameworks-technologies/graphicsview.qdoc
diff options
context:
space:
mode:
authorYann Bodson <yann.bodson@nokia.com>2009-08-31 00:29:56 (GMT)
committerYann Bodson <yann.bodson@nokia.com>2009-08-31 00:29:56 (GMT)
commitf5c0745622a914003aa75aaaa1e828854c1c85ba (patch)
tree6f9c27a22d5987a8bddd512222ab29dfeda5caf3 /doc/src/frameworks-technologies/graphicsview.qdoc
parent9cc59a858d116f75c19a782602ab8679405d9764 (diff)
parent9dade8d2e57655019ed4dc2fcdc4e226401138a2 (diff)
downloadQt-f5c0745622a914003aa75aaaa1e828854c1c85ba.zip
Qt-f5c0745622a914003aa75aaaa1e828854c1c85ba.tar.gz
Qt-f5c0745622a914003aa75aaaa1e828854c1c85ba.tar.bz2
Merge branch 'kinetic-declarativeui' of git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
Diffstat (limited to 'doc/src/frameworks-technologies/graphicsview.qdoc')
-rw-r--r--doc/src/frameworks-technologies/graphicsview.qdoc20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/src/frameworks-technologies/graphicsview.qdoc b/doc/src/frameworks-technologies/graphicsview.qdoc
index 8d7ea2c..397cb19 100644
--- a/doc/src/frameworks-technologies/graphicsview.qdoc
+++ b/doc/src/frameworks-technologies/graphicsview.qdoc
@@ -551,4 +551,24 @@
the widget is transformed resolution independently, allowing the
fonts and style to stay crisp when zoomed in. (Note that the effect
of resolution independence depends on the style.)
+
+ \section1 Performance
+
+ \section2 Floating Point Instructions
+
+ In order to accurately and quickly apply transformations and effects to
+ items, Graphics View is built with the assumption that the user's hardware
+ is able to provide reasonable performance for floating point instructions.
+
+ Many workstations and desktop computers are equipped with suitable hardware
+ to accelerate this kind of computation, but some embedded devices may only
+ provide libraries to handle mathematical operations or emulate floating
+ point instructions in software.
+
+ As a result, certain kinds of effects may be slower than expected on certain
+ devices. It may be possible to compensate for this performance hit by making
+ optimizations in other areas; for example, by using \l{#OpenGL Rendering}{OpenGL}
+ to render a scene. However, any such optimizations may themselves cause a
+ reduction in performance if they also rely on the presence of floating point
+ hardware.
*/