diff options
authorLaszlo Agocs <>2021-02-25 14:36:28 +0100
committerQt Cherry-pick Bot <>2021-02-26 11:32:41 +0000
commite966a340d09a9ffdc9876001a35201f38663ace7 (patch)
parentf35afe3eeaa460cb5e96171fb8a43fdf52c8761c (diff)
Fix typo in QQuickGraphicsConfiguration docs
Change-Id: Ia1ca8276560f913e84b9e4c119cd1ced89737790 Reviewed-by: Andy Nichols <> (cherry picked from commit 1a738838c4a199c61fce32c7eaba466181526335) Reviewed-by: Qt Cherry-pick Bot <>
1 files changed, 1 insertions, 1 deletions
diff --git a/src/quick/items/qquickgraphicsconfiguration.cpp b/src/quick/items/qquickgraphicsconfiguration.cpp
index 4d64cf0827..3e499ff12d 100644
--- a/src/quick/items/qquickgraphicsconfiguration.cpp
+++ b/src/quick/items/qquickgraphicsconfiguration.cpp
@@ -198,7 +198,7 @@ void QQuickGraphicsConfiguration::setDeviceExtensions(const QByteArrayList &exte
There are cases however, when allowing the 2D content write to the depth
buffer is not ideal. Consider a 3D scene as an "overlay" on top the 2D
scene, rendered via Qt Quick 3D using a \l View3D with
- \l{View3D::renderMode}}{renderMode} set to \c Overlay. In this case, having
+ \l{View3D::renderMode}{renderMode} set to \c Overlay. In this case, having
the depth buffer filled by 2D content can cause unexpected results. This is
because the way the 2D scene graph renderer generates and handles depth
values is not necessarily compatible with how a 3D scene works. This may end