Merge remote-tracking branch 'origin/4.12' into qds-1.59

Change-Id: I97a3ad2dc1ea9fddd3bd2853f84f6bc0ba2a442c

cmake/QtCreatorIDEBranding.cmake

@@ -1,9 +1,9 @@
 #BINARY_ARTIFACTS_BRANCH = master
 #PROJECT_USER_FILE_EXTENSION = .user
 
-set(IDE_VERSION "4.11.84")                            # The IDE version.
+set(IDE_VERSION "4.12.0")                            # The IDE version.
-set(IDE_VERSION_COMPAT "4.11.84")                     # The IDE Compatibility version.
+set(IDE_VERSION_COMPAT "4.12.0")                     # The IDE Compatibility version.
-set(IDE_VERSION_DISPLAY "4.12.0-rc1")                 # The IDE display version.
+set(IDE_VERSION_DISPLAY "4.12.0")                 # The IDE display version.
 set(IDE_COPYRIGHT_YEAR "2020")                        # The IDE current copyright year.
 
 set(IDE_SETTINGSVARIANT "QtProject")                  # The IDE settings variation.

dist/changes-4.11.2.md

@@ -33,6 +33,18 @@ Projects
 
 * Fixed wrong default project for adding files via wizards (QTCREATORBUG-23603)
 
+Debugging
+---------
+
+### CDB
+
+* Fixed startup if `_NT_DEBUGGER_EXTENSION_PATH` is set
+
+Test Integration
+----------------
+
+* Fixed debugging of Qt Quick tests (QTCREATORBUG-23709)
+
 Platforms
 ---------
 
@@ -46,8 +58,10 @@ Credits for these changes go to:
 André Pönitz  
 Andy Shaw  
 Christian Kandeler  
+Christian Stenger  
 David Schulz  
 Eike Ziller  
+Kai Köhne  
 Leena Miettinen  
 Orgad Shaneh  
 Richard Weickelt  

dist/changes-4.12.0.md

@@ -104,6 +104,7 @@ Projects
 
 ### Qbs
 
+* Updated included Qbs version to 1.16.0
 * Changed to use separate Qbs executable instead of direcly linking to Qbs (QTCREATORBUG-20622)
 * Added option for default install root (QTCREATORBUG-12983)
 
@@ -139,6 +140,7 @@ Analyzer
 ### Clang
 
 * Improved filtering
+* Added `Analyze Current File` to `Tools` menu and editor context menu
 * Added context menu item that opens help on diagnostics
 
 ### CppCheck
@@ -161,6 +163,7 @@ Qt Quick Designer
 * Added locking and pinning of animation curves (QDS-550, QDS-551)
 * Added support for annotations (QDS-39)
 * Fixed dragging of keyframes in curve editor (QDS-1405)
+* Fixed crash when selecting icon (QTCREATORBUG-23773)
 
 Version Control Systems
 -----------------------
@@ -181,6 +184,7 @@ Test Integration
 ### Google Test
 
 * Added support for internal logging (QTCREATORBUG-23354)
+* Added support for `GTEST_SKIP` (QTCREATORBUG-23736)
 
 Platforms
 ---------
@@ -198,10 +202,13 @@ Platforms
 
 ### Android
 
+* Discontinued support for Ministro
 * Added auto-detection of Java JDK (QTCREATORBUG-23407)
 * Added option to automatically download and install required Android tools (QTCREATORBUG-23285)
 * Added option to register multiple NDKs (QTCREATORBUG-23286)
 * Added automatic selection of correct NDK for Qt version (QTCREATORBUG-23583)
+* Added option to download and use [OpenSSL for Android](https://github.com/KDAB/android_openssl)
+  (QTBUG-80625)
 * Added support for Android 11 with API level 30
 * Improved examples browser to only show items tagged with `android` (QTBUG-80716)
 * Improved manifest editor (QTCREATORBUG-23283)
@@ -222,6 +229,10 @@ Platforms
 * Added support for J-Link and EBlink GDB servers
 * Added support for KEIL uVision v5.x debugger
 
+### MCU
+
+* Added auto-registration of documentation (UL-1685)
+
 Credits for these changes go to:
 --------------------------------
 Aleksei German  
@@ -243,6 +254,7 @@ Eike Ziller
 Fawzi Mohamed  
 Federico Guerinoni  
 Filippo Cucchetto  
+Friedemann Kleint  
 Halfdan Ingvarsson  
 Hannes Domani  
 Henning Gruendl  
@@ -266,6 +278,7 @@ Nikolai Kosjar
 Nikolay Panov  
 Oliver Wolff  
 Orgad Shaneh  
+Richard Weickelt  
 Robert Löhning  
 Sergey Morozov  
 Tasuku Suzuki  
@@ -276,6 +289,8 @@ Tim Jenssen
 Tobias Hunger  
 Topi Reinio  
 Ulf Hermann  
+Unseon Ryu  
+Venugopal Shivashankar  
 Vikas Pachdha  
 Ville Voutilainen  
 Volodymyr Samokhatko  

doc/README.md

@@ -14,6 +14,9 @@ the doc folder:
 - qtcreatordev
 - qtdesignstudio
 
+For more information, see:
+[Writing Documentation](https://doc.qt.io/qtcreator-extending/qtcreator-documentation.html)
+
 The Qt Design Studio Manual is based on the Qt Creator Manual, with
 additional topics. For more information, see the `README` file in the
 qtdesignstudio subfolder.
@@ -21,16 +24,20 @@ qtdesignstudio subfolder.
 The Extending Qt Creator Manual has its own sources. In addition, it
 pulls in API reference documentation from the Qt Creator source files.
 
-# QDoc Warnings
+# QDoc
 
 All the documents are built when you enter `make docs` on Linux or
-macOS or `nmake docs` on Windows. At the time of this writing, this
+macOS or `nmake docs` on Windows.
-leads to QDoc warnings being generated, because the Qt Creator Manual
-requires QDoc from Qt 5.14 or later (it links to new modules), whereas
-the Extending Qt Creator Manual requires QDoc from Qt 5.10 or earlier,
-because the doc configuration is not supported when using the Clang
-parser.
 
-To hide the doc errors and make doc builds faster, enter an option
+Since Qt Creator 4.12, you need to use QDoc Qt 5.14 or later to build
-to write the doc errors to the log. For example, on Windows enter
+the docs. While building with QDoc from Qt 5.11 or later technically
-`nmake docs 2> log.txt`.
+works, the Qt Creator Manual and Qt Design Studio Manual link to newer
+Qt modules, which means link errors will be printed.
+
+Please make the docs before submitting code changes to make sure that
+you do not introduce new QDoc warnings.
+
+While working on changes that introduce lots of warnings about missing API
+documentation, for example, you can enter an option to write the doc
+errors to the log. This helps make doc builds faster until you have
+fixed the errors. For example, on Windows enter `nmake docs 2> log.txt`.

doc/qtcreator/examples/transitions/Page1Form.ui.qml

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2017 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of Qt Creator
@@ -47,13 +47,20 @@
 ** $QT_END_LICENSE$
 **
 ****************************************************************************/
-import QtQuick 2.9
+import QtQuick 2.12
-import QtQuick.Controls 2.2
+import QtQuick.Controls 2.5
 
 Page {
     id: page
     width: 600
     height: 400
+    property alias mouseArea2: mouseArea2
+    property alias mouseArea1: mouseArea1
+    property alias mouseArea: mouseArea
+    property alias icon: icon
+    property alias bottomLeftRect: bottomLeftRect
+    property alias middleRightRect: middleRightRect
+    property alias topLeftRect: topLeftRect
 
     header: Label {
         text: qsTr("Page 1")
@@ -61,20 +68,12 @@ Page {
         padding: 10
     }
 
-    property alias icon: icon
-    property alias topLeftRect: topLeftRect
-    property alias bottomLeftRect: bottomLeftRect
-    property alias middleRightRect: middleRightRect
-
-    property alias mouseArea2: mouseArea2
-    property alias mouseArea1: mouseArea1
-    property alias mouseArea: mouseArea
-
     Image {
         id: icon
         x: 10
         y: 20
         source: "qt-logo.png"
+        fillMode: Image.PreserveAspectFit
     }
 
     Rectangle {
@@ -82,11 +81,11 @@ Page {
         width: 55
         height: 41
         color: "#00000000"
+        border.color: "#808080"
         anchors.left: parent.left
         anchors.leftMargin: 10
         anchors.top: parent.top
         anchors.topMargin: 20
-        border.color: "#808080"
 
         MouseArea {
             id: mouseArea
@@ -99,10 +98,10 @@ Page {
         width: 55
         height: 41
         color: "#00000000"
+        border.color: "#808080"
+        anchors.verticalCenter: parent.verticalCenter
         anchors.right: parent.right
         anchors.rightMargin: 10
-        anchors.verticalCenter: parent.verticalCenter
-        border.color: "#808080"
         MouseArea {
             id: mouseArea1
             anchors.fill: parent
@@ -114,14 +113,26 @@ Page {
         width: 55
         height: 41
         color: "#00000000"
+        border.color: "#808080"
         anchors.bottom: parent.bottom
         anchors.bottomMargin: 20
-        border.color: "#808080"
+        anchors.left: parent.left
+        anchors.leftMargin: 10
         MouseArea {
             id: mouseArea2
             anchors.fill: parent
         }
-        anchors.left: parent.left
+    }
-        anchors.leftMargin: 10
+
+    NumberAnimation {
+        id: numberAnimation
     }
 }
+
+/*##^##
+Designer {
+    D{i:0;formeditorZoom:0.75}D{i:4;anchors_height:100;anchors_width:100}D{i:6;anchors_height:100;anchors_width:100}
+D{i:8;anchors_height:100;anchors_width:100}
+}
+##^##*/
+

doc/qtcreator/examples/transitions/Page2Form.ui.qml

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2017 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of Qt Creator
@@ -47,8 +47,8 @@
 ** $QT_END_LICENSE$
 **
 ****************************************************************************/
-import QtQuick 2.9
+import QtQuick 2.12
-import QtQuick.Controls 2.2
+import QtQuick.Controls 2.5
 
 Page {
     width: 600

doc/qtcreator/examples/transitions/main.cpp

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2017 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of Qt Creator
@@ -47,20 +47,28 @@
 ** $QT_END_LICENSE$
 **
 ****************************************************************************/
-
 #include <QGuiApplication>
 #include <QQmlApplicationEngine>
 
 int main(int argc, char *argv[])
 {
+    if (qEnvironmentVariableIsEmpty("QTGLESSTREAM_DISPLAY")) {
+        qputenv("QT_QPA_EGLFS_PHYSICAL_WIDTH", QByteArray("213"));
+        qputenv("QT_QPA_EGLFS_PHYSICAL_HEIGHT", QByteArray("120"));
+
         QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
+    }
 
     QGuiApplication app(argc, argv);
 
     QQmlApplicationEngine engine;
-    engine.load(QUrl(QStringLiteral("qrc:/main.qml")));
+    const QUrl url(QStringLiteral("qrc:/main.qml"));
-    if (engine.rootObjects().isEmpty())
+    QObject::connect(&engine, &QQmlApplicationEngine::objectCreated,
-        return -1;
+                     &app, [url](QObject *obj, const QUrl &objUrl) {
+        if (!obj && url == objUrl)
+            QCoreApplication::exit(-1);
+    }, Qt::QueuedConnection);
+    engine.load(url);
 
     return app.exec();
 }

doc/qtcreator/examples/transitions/main.qml

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2017 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of Qt Creator
@@ -47,9 +47,8 @@
 ** $QT_END_LICENSE$
 **
 ****************************************************************************/
-
+import QtQuick 2.12
-import QtQuick 2.9
+import QtQuick.Controls 2.5
-import QtQuick.Controls 2.2
 
 ApplicationWindow {
     visible: true
@@ -64,7 +63,6 @@ ApplicationWindow {
 
         Page1Form {
             id: page
-
             mouseArea {
                 onClicked: stateGroup.state = ' '
             }
@@ -102,6 +100,7 @@ ApplicationWindow {
                 }
             }
         ]
+
         transitions: [
             Transition {
                 from: "*"; to: "State1"

doc/qtcreator/examples/transitions/transitions.pro

@@ -1,18 +1,20 @@
 QT += quick
+
 CONFIG += c++11
 
 # The following define makes your compiler emit warnings if you use
-# any feature of Qt which as been marked deprecated (the exact warnings
+# any Qt feature that has been marked deprecated (the exact warnings
-# depend on your compiler). Please consult the documentation of the
+# depend on your compiler). Refer to the documentation for the
-# deprecated API in order to know how to port your code away from it.
+# deprecated API to know how to port your code away from it.
 DEFINES += QT_DEPRECATED_WARNINGS
 
-# You can also make your code fail to compile if you use deprecated APIs.
+# You can also make your code fail to compile if it uses deprecated APIs.
 # In order to do so, uncomment the following line.
 # You can also select to disable deprecated APIs only up to a certain version of Qt.
 #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0
 
-SOURCES += main.cpp
+SOURCES += \
+        main.cpp
 
 RESOURCES += qml.qrc
 
@@ -26,3 +28,5 @@ QML_DESIGNER_IMPORT_PATH =
 qnx: target.path = /tmp/$${TARGET}/bin
 else: unix:!android: target.path = /opt/$${TARGET}/bin
 !isEmpty(target.path): INSTALLS += target
+
+DISTFILES +=

doc/qtcreator/images/creator_advanceduse.svg

@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.78,272H14.19C6.36,272,0,265.64,0,257.81V14.21C0,6.37,6.36,0.01,14.19,0.01h421.58
+		c7.84,0,14.19,6.36,14.19,14.19v243.6C449.97,265.64,443.61,272,435.78,272z"/>
+	<path fill="#878686" d="M0.44,19.66L0,14.19C0,6.36,6.35,0.01,14.18,0.01h421.61c7.83,0,14.18,6.35,14.18,14.18v6.84"/>
+	<circle fill="#DD5958" cx="17.43" cy="10.66" r="5"/>
+	<circle fill="#DBC558" cx="34.41" cy="10.66" r="5"/>
+	<circle fill="#52B257" cx="51.4" cy="10.66" r="5"/>
+</g>
+<path fill="#FFFFFF" d="M310.9,130.29c-5.72-1.44-12.54-1.96-19.95-2.96c-1.52-5.95-3.87-11.55-6.92-16.72
+	c4.57-6.01,9.08-11.24,12.13-16.37c0.86-1.44,1.03-3.56-0.1-4.69L282,75.49c-1.13-1.13-3.23-0.97-4.69-0.1
+	c-5.11,3.05-10.33,7.56-16.35,12.11c-5.11-3.01-10.66-5.35-16.55-6.9c-1.03-7.53-1.54-14.47-3.01-20.28
+	c-0.41-1.65-1.81-3.25-3.4-3.25h-19.89c-1.59,0-2.99,1.61-3.4,3.25c-1.46,5.76-1.96,12.66-2.99,20.13
+	c-5.91,1.5-11.49,3.81-16.61,6.79c-6.05-4.59-11.3-9.14-16.45-12.21c-1.44-0.86-3.56-1.01-4.69,0.1L159.92,89.2
+	c-1.13,1.13-0.97,3.25-0.1,4.69c3.03,5.11,7.51,10.29,12.04,16.26c-3.07,5.15-5.48,10.75-7.06,16.68
+	c-7.43,1.01-14.31,1.52-20.05,2.99c-1.65,0.41-3.25,1.79-3.25,3.38v19.89c0,1.59,1.61,2.99,3.25,3.4
+	c5.68,1.44,12.43,1.96,19.78,2.94c1.5,6.03,3.85,11.73,6.9,16.98c-4.51,5.91-8.93,11.08-11.96,16.12c-0.86,1.46-1.01,3.58,0.1,4.69
+	l14.06,14.06c1.13,1.13,3.25,0.97,4.69,0.1c5-2.96,10.11-7.35,15.93-11.8c5.25,3.15,10.97,5.58,17.05,7.16
+	c0.99,7.31,1.5,14.04,2.94,19.72c0.41,1.63,1.79,3.23,3.38,3.23c6.63,0,13.26,0,19.89,0c1.59,0,2.99-1.61,3.4-3.23
+	c1.42-5.64,1.93-12.33,2.92-19.58c6.07-1.54,11.82-3.93,17.09-7.04c5.89,4.47,11.01,8.87,16.04,11.88c1.46,0.86,3.58,1.03,4.69-0.1
+	l14.06-14.06c1.13-1.13,0.97-3.23,0.1-4.69c-2.99-5.02-7.39-10.15-11.86-16.02c3.09-5.23,5.48-10.91,7.02-16.92
+	c7.39-1.01,14.21-1.52,19.93-2.96c1.63-0.41,3.23-1.81,3.23-3.4v-19.89C314.13,132.1,312.53,130.7,310.9,130.29z M227.41,175.67
+	c-18.07,0-32.71-14.65-32.71-32.71s14.65-32.71,32.71-32.71s32.71,14.65,32.71,32.71S245.48,175.67,227.41,175.67z"/>
+</svg>

doc/qtcreator/images/creator_buildingrunning.svg

@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M377.11,224.13H33.89c-7.84,0-14.19-6.36-14.19-14.19V13.71c0-7.84,6.36-14.19,14.19-14.19h343.21
+		c7.84,0,14.19,6.36,14.19,14.19v196.23C391.3,217.78,384.95,224.13,377.11,224.13z"/>
+	<path fill="#878686" d="M20.06,15.74l-0.37-4.51c0-6.47,5.24-11.71,11.71-11.71h348.18c6.47,0,11.71,5.24,11.71,11.71v5.65"/>
+	<circle fill="#DD5958" cx="34.09" cy="8.31" r="4.13"/>
+	<circle fill="#DBC558" cx="48.12" cy="8.31" r="4.13"/>
+	<circle fill="#52B257" cx="62.14" cy="8.31" r="4.13"/>
+</g>
+<rect x="63.92" y="25.97" fill="#949292" width="277.09" height="185.41"/>
+<g>
+	<path fill="none" stroke="#FFFFFF" stroke-width="7.8665" stroke-linecap="round" stroke-miterlimit="10" d="M153.93,111.58
+		c0-26.07,21.13-47.2,47.2-47.2s47.2,21.13,47.2,47.2s-21.13,47.2-47.2,47.2"/>
+	<circle fill="#FFFFFF" cx="200.14" cy="111.25" r="21.12"/>
+	<text transform="matrix(1 0 0 1 123.5649 108.1074)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="26.1845px">1</text>
+	<text transform="matrix(1 0 0 1 248.9873 71.7993)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="26.1845px">2</text>
+	<text transform="matrix(1 0 0 1 202.1196 190.623)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="26.1845px">3</text>
+</g>
+<g>
+	<g>
+		<path fill="#C9C7C7" d="M412.27,272h-73c-7.84,0-14.19-6.36-14.19-14.19V89.58c0-7.84,6.36-14.19,14.19-14.19h73
+			c7.84,0,14.19,6.36,14.19,14.19v168.22C426.47,265.64,420.11,272,412.27,272z"/>
+		<path fill="#878686" d="M325.4,89.59l-0.32-3.95c0-5.66,4.59-10.25,10.25-10.25h80.88c5.66,0,10.25,4.59,10.25,10.25v4.94"/>
+	</g>
+	
+		<rect x="302.37" y="133.85" transform="matrix(-1.836970e-16 1 -1 -1.836970e-16 551.7495 -200.3197)" fill="#949292" width="147.32" height="83.73"/>
+	<g>
+		<path fill="none" stroke="#FFFFFF" stroke-width="3.7066" stroke-linecap="round" stroke-miterlimit="10" d="M355.31,172.15
+			c0-12.28,9.96-22.24,22.24-22.24c12.28,0,22.24,9.96,22.24,22.24c0,12.28-9.96,22.24-22.24,22.24"/>
+		<circle fill="#FFFFFF" cx="377.08" cy="171.99" r="9.95"/>
+		<text transform="matrix(1 0 0 1 341 170.5078)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.338px">1</text>
+		<text transform="matrix(1 0 0 1 400.0977 153.4004)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.338px">2</text>
+		<text transform="matrix(1 0 0 1 378.0137 209.3896)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.338px">3</text>
+	</g>
+</g>
+</svg>

doc/qtcreator/images/creator_coding.svg

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.81,271.62H14.41c-7.84,0-14.19-6.36-14.19-14.19V13.94c0-7.84,6.36-14.19,14.19-14.19h421.4
+		c7.84,0,14.19,6.36,14.19,14.19v243.49C450,265.27,443.64,271.62,435.81,271.62z"/>
+	<path fill="#878686" d="M0.66,19.38l-0.44-5.46c0-7.83,6.35-14.18,14.18-14.18h421.43c7.83,0,14.18,6.35,14.18,14.18v6.84"/>
+	<circle fill="#DD5958" cx="17.63" cy="10.39" r="4.99"/>
+	<circle fill="#DBC558" cx="34.61" cy="10.39" r="4.99"/>
+	<circle fill="#52B257" cx="51.59" cy="10.39" r="4.99"/>
+</g>
+<rect x="66.15" y="30.54" fill="#444345" width="343.54" height="233.69"/>
+<rect x="40.18" y="30.54" fill="#333333" width="25.97" height="233.69"/>
+<text transform="matrix(1 0 0 1 51.6992 49.5161)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">1</text>
+<text transform="matrix(1 0 0 1 51.6992 67.8916)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">2</text>
+<text transform="matrix(1 0 0 1 51.6992 86.2676)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">3</text>
+<text transform="matrix(1 0 0 1 51.6992 104.6431)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">4</text>
+<text transform="matrix(1 0 0 1 51.6992 123.0186)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">5</text>
+<text transform="matrix(1 0 0 1 51.6992 141.3945)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">6</text>
+<text transform="matrix(1 0 0 1 51.6992 159.7695)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">7</text>
+<text transform="matrix(1 0 0 1 51.6992 178.1455)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">8</text>
+<text transform="matrix(1 0 0 1 51.6992 196.5215)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">9</text>
+<text transform="matrix(1 0 0 1 43.3105 214.8965)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">10</text>
+<text transform="matrix(1 0 0 1 43.3105 233.2725)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">11</text>
+<text transform="matrix(1 0 0 1 43.3105 251.6484)" fill="#FFFFFF" font-family="'IBMPlexMono'" font-size="13.9815px">12</text>
+<text transform="matrix(1 0 0 1 78.064 49.5161)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">// main.cpp</text>
+<text transform="matrix(1 0 0 1 78.064 67.8916)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">#include &lt;QApplication&gt;</text>
+<text transform="matrix(1 0 0 1 78.064 86.2676)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">#include &lt;QTableView&gt;</text>
+<text transform="matrix(1 0 0 1 78.064 104.6431)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">#include &quot;mymodel.h&quot;</text>
+<text transform="matrix(1 0 0 1 78.064 141.3945)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">int main(int argc, char *argv[])</text>
+<text transform="matrix(1 0 0 1 78.064 178.1455)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">{</text>
+<text transform="matrix(1 0 0 1 78.064 196.5215)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">    QApplication a(argc, argv);</text>
+<text transform="matrix(1 0 0 1 78.064 214.8965)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">    QTableView tableView;</text>
+<text transform="matrix(1 0 0 1 78.064 233.2725)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">    MyModel myModel;</text>
+<text transform="matrix(1 0 0 1 78.064 251.6484)" fill="#FFFFFF" font-family="'IBMPlexMono-Light'" font-size="13.9815px">}</text>
+</svg>

doc/qtcreator/images/creator_designinguserinterface.svg

@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.81,271.62H14.83c-7.84,0-14.19-6.36-14.19-14.19V14.19C0.63,6.36,6.99,0,14.83,0h420.98
+		C443.64,0,450,6.36,450,14.19v243.23C450,265.27,443.64,271.62,435.81,271.62z"/>
+	<path fill="#878686" d="M1.08,19.62l-0.44-5.45C0.63,6.34,6.97,0,14.8,0h421.04C443.66,0,450,6.34,450,14.16v6.83"/>
+	<circle fill="#DD5958" cx="18.04" cy="10.64" r="4.99"/>
+	<circle fill="#DBC558" cx="35" cy="10.64" r="4.99"/>
+	<circle fill="#52B257" cx="51.96" cy="10.64" r="4.99"/>
+</g>
+<path fill="#949292" d="M98.62,245.03H18.8c-2.75,0-5-2.25-5-5V47.72c0-2.75,2.25-5,5-5h79.81c2.75,0,5,2.25,5,5v192.3
+	C103.62,242.78,101.37,245.03,98.62,245.03z"/>
+<path fill="none" stroke="#FFFFFF" stroke-width="11.8898" stroke-linecap="round" stroke-miterlimit="10" d="M177.01,125.88
+	c0-39.4,31.94-71.34,71.34-71.34s71.34,31.94,71.34,71.34s-31.94,71.34-71.34,71.34"/>
+<path fill="none" stroke="#FFFFFF" stroke-width="2.5935" stroke-linecap="round" stroke-miterlimit="10" d="M44.02,68.87
+	c0-8.59,6.97-15.56,15.56-15.56s15.56,6.97,15.56,15.56s-6.97,15.56-15.56,15.56"/>
+<circle fill="#FFFFFF" cx="246.85" cy="125.38" r="31.93"/>
+<polygon fill="#878686" points="252.27,115.11 247.86,173.16 266.03,151.21 293.54,155.76 "/>
+<text transform="matrix(1 0 0 1 131.1162 120.6279)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="39.5765px">1</text>
+<text transform="matrix(1 0 0 1 320.6885 65.7515)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="39.5765px">2</text>
+<text transform="matrix(1 0 0 1 249.8477 245.3447)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="39.5765px">3</text>
+<g>
+	<path fill="#FFFFFF" d="M72.84,134.43H42.91c-2.75,0-5-2.25-5-5v-9.3c0-2.75,2.25-5,5-5h29.93c2.75,0,5,2.25,5,5v9.3
+		C77.84,132.18,75.59,134.43,72.84,134.43z"/>
+	<text transform="matrix(1 0 0 1 49.1719 128.6772)" fill="#C9C7C7" font-family="'TitilliumWeb-Bold'" font-size="11.9663px">ON</text>
+</g>
+<g>
+	<path fill="#FFFFFF" d="M57.58,180.2h0.19c0.62,0,1.13-0.51,1.13-1.13v-10.95c0-0.62-0.51-1.13-1.13-1.13h-0.19
+		c-0.62,0-1.13,0.51-1.13,1.13v10.95C56.45,179.69,56.96,180.2,57.58,180.2z"/>
+	<path fill="#FFFFFF" d="M84.49,175.31H31.25c-0.95,0-1.72-0.77-1.72-1.72v0c0-0.95,0.77-1.72,1.72-1.72h53.23
+		c0.95,0,1.72,0.77,1.72,1.72v0C86.21,174.54,85.43,175.31,84.49,175.31z"/>
+	<path fill="#E0E1E0" d="M58.93,171.87h25.55c0.95,0,1.73,0.77,1.73,1.72v0c0,0.95-0.78,1.72-1.73,1.72H58.93V171.87z"/>
+</g>
+<g>
+	<path fill="none" stroke="#FFFFFF" stroke-width="0.5769" stroke-miterlimit="10" d="M74.13,228.45H42.6
+		c-6.13,0-11.15-5.02-11.15-11.15v0c0-6.13,5.02-11.15,11.15-11.15h31.54c6.13,0,11.15,5.02,11.15,11.15v0
+		C85.29,223.43,80.27,228.45,74.13,228.45z"/>
+	<circle fill="#FFFFFF" cx="43.65" cy="217.2" r="7.88"/>
+</g>
+<line fill="none" stroke="#C9C7C7" stroke-width="0.9977" stroke-miterlimit="10" x1="13.16" y1="98.25" x2="103.47" y2="98.25"/>
+<line fill="none" stroke="#C9C7C7" stroke-width="0.9977" stroke-miterlimit="10" x1="13.16" y1="150.11" x2="103.47" y2="150.11"/>
+<line fill="none" stroke="#C9C7C7" stroke-width="0.9977" stroke-miterlimit="10" x1="13.16" y1="195.79" x2="103.47" y2="195.79"/>
+</svg>

doc/qtcreator/images/creator_gettinghelp.svg

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C8C6C6" d="M435.91,272.12H15.19C7.36,272.12,1,265.76,1,257.92V14.85C1,7.01,7.36,0.66,15.19,0.66h420.71
+		c7.84,0,14.19,6.36,14.19,14.19v243.07C450.1,265.76,443.75,272.12,435.91,272.12z"/>
+	<path fill="#868585" d="M1.44,20.26L1,14.81C1,6.99,7.34,0.66,15.15,0.66h420.79c7.82,0,14.15,6.34,14.15,14.15v6.83"/>
+	<circle fill="#DC5958" cx="18.39" cy="11.29" r="4.99"/>
+	<circle fill="#DAC457" cx="35.35" cy="11.29" r="4.99"/>
+	<circle fill="#51B156" cx="52.3" cy="11.29" r="4.99"/>
+</g>
+<circle fill="#FFFFFF" cx="222.34" cy="144.43" r="64.54"/>
+<rect x="208.26" y="124.62" fill="none" width="314.12" height="137.75"/>
+<text transform="matrix(1 0 0 1 208.2568 170.8926)" fill="#C8C6C6" font-family="'TitilliumWeb-Bold'" font-size="71.7954px">?</text>
+</svg>

doc/qtcreator/images/creator_gettingstarted.svg

@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.78,272H15.41c-7.84,0-14.19-6.36-14.19-14.19V14.94c0-7.84,6.36-14.19,14.19-14.19h420.37
+		c7.84,0,14.19,6.36,14.19,14.19v242.86C449.97,265.64,443.61,272,435.78,272z"/>
+	<path fill="#878686" d="M1.66,20.34l-0.44-5.45c0-7.81,6.33-14.14,14.14-14.14h420.47c7.81,0,14.14,6.33,14.14,14.14v6.82"/>
+	<circle fill="#DD5958" cx="18.6" cy="11.37" r="4.98"/>
+	<circle fill="#DBC558" cx="35.53" cy="11.37" r="4.98"/>
+	<circle fill="#52B257" cx="52.47" cy="11.37" r="4.98"/>
+</g>
+<g>
+	<g>
+		<path fill="#FFFFFF" d="M303.47,70.58c-2.26,40.17-11.3,68.54-51.47,101.18c0,17.07-6.78,34.15-20.59,46.2l-22.85-25.61
+			c-4.77,4.52-11.05,6.78-17.07,7.03c-8.03,0.25-15.82-2.76-21.59-9.04c-10.04-11.3-9.04-28.62,2.01-38.66l-22.85-25.61
+			c13.81-12.3,31.38-17.32,48.46-15.32C234.17,74.35,263.3,68.32,303.47,70.58z M261.79,132.34c7.53-6.78,8.03-18.08,1.51-25.61
+			c-3.77-4.02-8.79-6.28-14.31-6.03c-4.27,0.25-8.29,1.76-11.3,4.52c-7.53,6.78-8.03,18.08-1.51,25.61
+			c3.77,4.02,8.79,6.28,14.31,6.03C254.51,136.61,258.53,135.11,261.79,132.34z"/>
+	</g>
+</g>
+</svg>

doc/qtcreator/images/creator_managingprojects.svg

@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M434.78,272H14.41c-7.84,0-14.19-6.36-14.19-14.19V14.94c0-7.84,6.36-14.19,14.19-14.19h420.37
+		c7.84,0,14.19,6.36,14.19,14.19V257.8C448.97,265.64,442.61,272,434.78,272z"/>
+	<path fill="#878686" d="M0.66,20.34l-0.44-5.45c0-7.81,6.33-14.14,14.14-14.14h420.47c7.81,0,14.14,6.33,14.14,14.14v6.82"/>
+	<circle fill="#DD5958" cx="17.6" cy="11.37" r="4.98"/>
+	<circle fill="#DBC558" cx="34.53" cy="11.37" r="4.98"/>
+	<circle fill="#52B257" cx="51.47" cy="11.37" r="4.98"/>
+</g>
+<g transform="translate(0,-280.06666)">
+	<path fill="#878686" d="M154.99,354.72c-3,0-5.44,2.44-5.44,5.44l0,0v27.15v97.8c0,3,2.44,5.44,5.44,5.44h141.27
+		c3,0,5.44-2.44,5.44-5.44v-97.8c0-3-2.44-5.44-5.44-5.44H252.9l-17.39-24.85c-1.02-1.45-2.68-2.31-4.45-2.31h-76.07V354.72z"/>
+</g>
+<path fill="#878686" d="M107.69,205.06h-96.9V79.34h79.11c0.34,0,17.09,18.5,17.79,17.79C107.69,97.14,107.69,205.06,107.69,205.06z
+	"/>
+<path fill="#878686" d="M440.85,206.15h-96.9V80.43h79.11c0.34,0,17.09,18.5,17.79,17.79L440.85,206.15L440.85,206.15z"/>
+<text transform="matrix(1 0 0 1 14.9414 160.6211)" fill="#F2F2F3" font-family="'TitilliumWeb-Regular'" font-size="52.0199px">C++</text>
+<text transform="matrix(1 0 0 1 349.8203 164.9639)" fill="#F2F2F3" font-family="'TitilliumWeb-Regular'" font-size="52.0199px">qml</text>
+<polygon fill="#F2F2F3" points="200.89,150.65 162.96,128.75 162.96,172.55 "/>
+<rect x="288.68" y="143.6" fill="#F2F2F3" width="55.28" height="16.26"/>
+<rect x="107.69" y="143.6" fill="#F2F2F3" width="55.28" height="16.26"/>
+<polygon fill="#F2F2F3" points="250.75,150.65 288.68,172.55 288.68,128.75 "/>
+</svg>

doc/qtcreator/images/creator_publishing.svg

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.78,272H15.41c-7.84,0-14.19-6.36-14.19-14.19V14.94c0-7.84,6.36-14.19,14.19-14.19h420.37
+		c7.84,0,14.19,6.36,14.19,14.19v242.86C449.97,265.64,443.61,272,435.78,272z"/>
+	<path fill="#878686" d="M1.66,20.34l-0.44-5.45c0-7.81,6.33-14.14,14.14-14.14h420.47c7.81,0,14.14,6.33,14.14,14.14v6.82"/>
+	<circle fill="#DD5958" cx="18.6" cy="11.37" r="4.98"/>
+	<circle fill="#DBC558" cx="35.53" cy="11.37" r="4.98"/>
+	<circle fill="#52B257" cx="52.47" cy="11.37" r="4.98"/>
+</g>
+<path fill="#EEEDEE" d="M409.72,257.05H52.05c-2.75,0-5-2.25-5-5V34.88c0-2.75,2.25-5,5-5h357.67c2.75,0,5,2.25,5,5v217.18
+	C414.72,254.8,412.47,257.05,409.72,257.05z"/>
+<g>
+	<polygon fill="#949292" points="207.47,103.17 251.2,103.17 289.47,168.77 341.4,168.77 363.27,122.31 385.13,122.31 
+		352.33,187.91 275.8,187.91 237.53,122.31 210.2,122.31 	"/>
+	<polygon fill="#949292" points="305.87,81.31 327.73,81.31 327.73,125.04 344.13,125.04 316.8,152.37 289.47,125.04 305.87,125.04 
+			"/>
+	<circle fill="#949292" cx="289.47" cy="201.57" r="10.93"/>
+	<circle fill="#949292" cx="338.67" cy="201.57" r="10.93"/>
+</g>
+<g>
+	<g>
+		<path fill="#C9C7C7" d="M169.36,247.01h-76.9c-7.84,0-14.19-6.36-14.19-14.19V57.03c0-7.84,6.36-14.19,14.19-14.19h76.9
+			c7.84,0,14.19,6.36,14.19,14.19v175.79C183.55,240.65,177.2,247.01,169.36,247.01z"/>
+		<path fill="#878686" d="M78.6,57.58l-0.33-4.1c0-5.88,4.77-10.65,10.65-10.65h83.99c5.88,0,10.65,4.77,10.65,10.65v5.14"/>
+	</g>
+	
+		<rect x="54.69" y="103.54" transform="matrix(-1.836970e-16 1 -1 -1.836970e-16 278.2001 15.8358)" fill="#949292" width="152.99" height="86.95"/>
+	<g>
+		<path fill="none" stroke="#FFFFFF" stroke-width="3.8493" stroke-linecap="round" stroke-miterlimit="10" d="M109.66,143.31
+			c0-12.76,10.34-23.1,23.1-23.1s23.1,10.34,23.1,23.1s-10.34,23.1-23.1,23.1"/>
+		<circle fill="#FFFFFF" cx="132.27" cy="143.15" r="10.34"/>
+		<text transform="matrix(1 0 0 1 94.7988 141.6104)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.8129px">1</text>
+		<text transform="matrix(1 0 0 1 156.1709 123.8447)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.8129px">2</text>
+		<text transform="matrix(1 0 0 1 133.2363 181.9883)" fill="#FFFFFF" font-family="'TitilliumWeb-Bold'" font-size="12.8129px">3</text>
+	</g>
+</g>
+</svg>

doc/qtcreator/images/creator_testing.svg

@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 24.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" baseProfile="tiny" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+	 x="0px" y="0px" viewBox="0 0 450 272" xml:space="preserve">
+<g>
+	<path fill="#C9C7C7" d="M435.78,272H15.41c-7.84,0-14.19-6.36-14.19-14.19V14.94c0-7.84,6.36-14.19,14.19-14.19h420.37
+		c7.84,0,14.19,6.36,14.19,14.19v242.86C449.97,265.64,443.61,272,435.78,272z"/>
+	<path fill="#878686" d="M1.66,20.34l-0.44-5.45c0-7.81,6.33-14.14,14.14-14.14h420.47c7.81,0,14.14,6.33,14.14,14.14v6.82"/>
+	<circle fill="#DD5958" cx="18.6" cy="11.37" r="4.98"/>
+	<circle fill="#DBC558" cx="35.53" cy="11.37" r="4.98"/>
+	<circle fill="#52B257" cx="52.47" cy="11.37" r="4.98"/>
+</g>
+<path fill="#EEEDEE" d="M409.72,257.05H52.05c-2.75,0-5-2.25-5-5V34.88c0-2.75,2.25-5,5-5h357.67c2.75,0,5,2.25,5,5v217.18
+	C414.72,254.8,412.47,257.05,409.72,257.05z"/>
+<polygon fill="#949292" points="330.22,140.56 167,46.32 167,234.8 "/>
+<g>
+	<path fill="#EEEDEE" d="M225.27,119.2c0.11-0.35,0.23-0.69,0.36-1.02c0.49-1.19,1.22-2.31,2.15-3.25c2.33-2.35,5.63-3.33,9.06-2.98
+		c0.07-2.23,0.54-4.36,1.35-6.15c1.14-2.5,2.95-4.45,5.2-5.36c1-0.39,2.13,0.09,2.52,1.08c0.41,0.98-0.07,2.11-1.06,2.5
+		c-1.28,0.52-2.39,1.76-3.13,3.39c-0.7,1.56-1.08,3.44-1.01,5.42c2.29,0.85,4.5,2.24,6.43,4.15c1.91,1.89,3.32,4.09,4.19,6.37
+		c1.98,0.05,3.86-0.34,5.41-1.06c1.63-0.76,2.85-1.87,3.36-3.16c0.4-0.98,1.51-1.48,2.49-1.09c1,0.38,1.48,1.51,1.11,2.51
+		c-0.89,2.25-2.82,4.08-5.31,5.24c-1.78,0.83-3.89,1.34-6.13,1.41c0.38,3.43-0.56,6.74-2.89,9.09c-0.94,0.94-2.05,1.68-3.23,2.18
+		c-0.33,0.14-0.67,0.25-1.02,0.37c0.06,0.44,0.12,0.88,0.16,1.34c0.22,2.97-0.11,5.82-0.92,8.45l10.51,3.39l7.86-5.01
+		c0.9-0.6,2.09-0.34,2.67,0.58c0.58,0.88,0.32,2.07-0.58,2.67l-8.65,5.53c-0.5,0.31-1.09,0.37-1.63,0.22l-11.63-3.77
+		c-1.24,2.48-2.88,4.75-4.84,6.74l-0.21,0.21l7.81,8.96c0.42,0.46,0.56,1.05,0.47,1.61l-1.07,8.56c-0.13,1.06-1.09,1.83-2.16,1.68
+		c-1.06-0.13-1.79-1.09-1.68-2.16l0.96-7.8l-7.29-8.33c-1.66,1.26-3.46,2.34-5.36,3.21c-1.51,0.72-3.08,1.3-4.69,1.73l2.07,11.49
+		c0.08,0.5-0.01,0.98-0.26,1.38l-3.58,5.81c-0.57,0.92-1.76,1.2-2.66,0.65c-0.92-0.57-1.2-1.76-0.65-2.66l3.22-5.22l-1.91-10.68
+		c-0.48,0.06-0.96,0.12-1.44,0.14c-6.18,0.49-12.29-1.25-16.88-5.79c-4.61-4.57-6.4-10.66-5.97-16.84c0.02-0.48,0.07-0.96,0.13-1.44
+		l-10.7-1.81l-5.19,3.27c-0.9,0.56-2.09,0.3-2.67-0.62c-0.56-0.9-0.3-2.09,0.62-2.67l5.78-3.63c0.4-0.25,0.88-0.35,1.38-0.28
+		l11.5,1.96c0.41-1.61,0.98-3.19,1.69-4.71c0.85-1.9,1.92-3.71,3.16-5.39l-8.4-7.22l-7.79,1.03c-1.05,0.14-2.04-0.6-2.18-1.66
+		c-0.14-1.05,0.6-2.04,1.66-2.18l8.55-1.15c0.56-0.1,1.15,0.03,1.61,0.45l9.06,7.75l0.21-0.21c1.97-1.99,4.2-3.67,6.67-4.92
+		l-3.85-11.57c-0.18-0.56-0.12-1.15,0.18-1.65l5.45-8.7c0.59-0.9,1.78-1.18,2.66-0.61c0.92,0.57,1.2,1.76,0.61,2.66l-4.93,7.91
+		l3.48,10.48c2.64-0.82,5.46-1.2,8.44-1C224.39,119.09,224.83,119.15,225.27,119.2z"/>
+</g>
+</svg>

doc/qtcreator/src/analyze/creator-analyze.qdoc

@@ -45,8 +45,9 @@
 
     You can drag and drop the views in the \uicontrol Debug mode to new
     positions on the screen. The size and position of views are saved for future
-    sessions. Select \uicontrol {Window > Views > Reset to Default Layout} to
+    sessions. Select \uicontrol Window > \uicontrol Views >
-    reset the views to their original sizes and positions.
+    \uicontrol {Reset to Default Layout} to reset the views to their original
+    sizes and positions.
 
     You can use the following code analysis tools in the \uicontrol Debug
     mode:

doc/qtcreator/src/analyze/creator-clang-static-analyzer.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2019 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -67,6 +67,9 @@
 
     \section1 Running Clang Tools
 
+    To run the Clang tools to analyze the currently open file, select
+    \uicontrol Tools > \uicontrol {C++} > \uicontrol {Analyze Current File}.
+
     To run the Clang tools to analyze an open project:
 
     \list 1
@@ -96,9 +99,19 @@
     the code editor.
 
     If a fixit exists for an issue, you can select the check box next to the
-    issue to schedule it for fixing. You can see the status of the issue by
+    issue to schedule it for fixing. Select the \uicontrol {Select Fixits}
+    check box to select all fixits. You can see the status of an issue by
     hovering the mouse pointer over the icon next to the check box.
 
+    To see more information about an issue that is marked with the
+    \inlineimage refactormarker.png
+    icon, hover the mouse pointer over the line.
+
+    Select the \inlineimage settings.png
+    button to configure Clang diagnostics globally for Clang tools.
+
+    \image qtcreator-clang-tools-options-customized.png "Clang Tools customized settings"
+
     \section1 Configuring Clang Tools
 
     To configure Clang diagnostics globally for Clang tools:
@@ -131,32 +144,28 @@
         \li In the \uicontrol {Diagnostic configuration name} field, give the
             configuration a name, and then select \uicontrol OK.
 
-        \li In the \uicontrol Clang tab, select the
+        \li In the \uicontrol {Clang Warnings} tab, select the
             \uicontrol {Use diagnostic flags from the build system} check box
             to forward diagnostic flags, such as warning flags, from the build
             system to the Clang code model for displaying annotations in the
             code editor.
 
-        \li In the \uicontrol {Clang-Tidy} tab, select
+        \li In the \uicontrol {Clang-Tidy Checks} tab, select
-            \uicontrol {Select Checks} to select the checks to perform,
+            \uicontrol {Select Checks} to select the checks to perform.
-            \uicontrol {Use .clang-tidy Config File} to read them from a
-            Clang-Tidy configuration file, or \uicontrol Disable to disable
-            them.
 
-            \image qtcreator-clang-tidy.png "Clang-Tidy tab"
+            \image qtcreator-clang-tidy.png "Clang-Tidy Checks tab"
 
-        \li Select the \uicontrol {Web Page} link to view more
+            For more information about the available checkers, see
-            information about the available checkers in the
             \l{https://clang-analyzer.llvm.org/available_checks.html}
             {Clang Static Analyzer documentation}.
 
         \li To edit the selected check as plain text, select
             \uicontrol {Edit Checks as String}.
 
-        \li In the \uicontrol Clazy tab, select the level of Clazy
+        \li In the \uicontrol {Clazy Checks} tab, select the level of Clazy
             checks to perform.
 
-            \image qtcreator-clazy.png "Clazy tab"
+            \image qtcreator-clazy.png "Clazy Checks tab"
 
         \li In the \uicontrol {Topic Filter} field, select a topic to view
             only checks related to that area in the \uicontrol Checks field.

doc/qtcreator/src/analyze/creator-cppcheck.qdoc

@@ -38,20 +38,29 @@
     The experimental Cppcheck Diagnostics plugin integrates diagnostics
     that are generated by the Cppcheck tool into the C++ editor.
 
-    To enable running Cppcheck automatically on currently open files:
+    Cppcheck is automatically run on open files. To select the files to
+    check in the currently active project, select \uicontrol Analyze >
+    \uicontrol Cppcheck.
+
+    \section1 Enabling the Cppcheck Plugin
+
+    To enable the Cppcheck plugin:
 
     \list 1
         \li Select \uicontrol Help > \uicontrol {About Plugins} >
             \uicontrol {Code Analyzer} > \uicontrol Cppcheck to enable the
             plugin.
         \li Select \uicontrol {Restart Now} to restart \QC and load the plugin.
-        \li Select \uicontrol Tools > \uicontrol Options > \uicontrol Analyzer
+    \endlist
-            > \uicontrol Cppcheck to specify settings for running Cppcheck.
+
-            \image qtcreator-cppcheck-options.png "Cppcheck options"
+    \section1 Running Cppcheck on Selected Files
+
+    \list 1
+        \li Select \uicontrol Analyze > \uicontrol Cppcheck.
+            \image qtcreator-cppcheck-run-configuration.png "Cppcheck run configuration"
         \li In the \uicontrol Binary field, enter the path to the Cppcheck
             executable file.
-        \li In the \uicontrol Checks group, select the checks to perform on
+        \li In the \uicontrol Checks group, select the checks to perform.
-            currently open files.
             \note By default, Cppcheck uses multiple threads to perform checks.
             Selecting the \uicontrol {Unused functions} option disables the
             default behavior.
@@ -78,8 +87,14 @@
             calculate additional arguments based on current project's settings
             (such as the language used and standard version) and pass them to
             Cppcheck.
+        \li Select the files to run Cppcheck on.
+        \li Select \uicontrol Analyze.
     \endlist
 
-    \QC automatically runs Cppcheck on currently opened documents and displays
+    \QC runs Cppcheck on the selected files and displays results via text
-    results via text marks or annotations.
+    marks or annotations.
+
+    To specify the settings above for the automatically run checks,
+    select \uicontrol Tools > \uicontrol Options > \uicontrol Analyzer
+    > \uicontrol Cppcheck.
 */

doc/qtcreator/src/analyze/creator-ctf-visualizer.qdoc

@@ -97,6 +97,10 @@
     To reset the default zoom level, right-click the timeline to open the
     context menu, and select \uicontrol {Reset Zoom}.
 
+    Select the \inlineimage filtericon.png
+    (\uicontrol {Restrict to Threads}) button (10) to select the threads to
+    show.
+
     \section2 Selecting Event Ranges
 
     You can select an event range (8) to view the time it represents or to zoom

doc/qtcreator/src/analyze/creator-heob.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2018 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -41,12 +41,17 @@
     for detecting buffer overruns and memory leaks. You must download and
     install Heob to run it from \QC.
 
+    \image qtcreator-heob-settings.png
+
     To run Heob on the currently open project:
 
     \list 1
 
         \li Select \uicontrol Analyze > \uicontrol Heob.
 
+        \li Select the Heob settings profile to use, or select \uicontrol New
+            to create a new profile.
+
         \li In the \uicontrol {Heob path} field, enter the path to the Heob
             executable.
 
@@ -72,8 +77,6 @@
 
     To specify settings for Heob, select \uicontrol Analyze > \uicontrol Heob.
 
-    \image qtcreator-heob-settings.png
-
     In the \uicontrol {Extra arguments} field, enter additional arguments for
     running Heob. To list the available arguments in the Heob console, enter
     \c -H in this field and press \key Enter.
@@ -83,7 +86,10 @@
     leaks visually in the file and the \c -L1024 option to record leak contents
     up to 1024 bytes in the file. For example, \c {-oleaks.html -g2 -L1024}
 
-    Select \uicontrol Save to save the current settings as default.
+    To save the settings profile, select \uicontrol Save.
+
+    To remove a customized settings profile, select the profile, and then
+    select \uicontrol Delete.
 
     The following sections describe the available options in more detail.
 

doc/qtcreator/src/analyze/creator-valgrind-overview.qdoc

@@ -59,9 +59,9 @@
     For more information about analyzing applications for which you do not have
     a project, see \l{Running Valgrind Tools on External Applications}.
 
-    To select options for the Valgrind tools, select \uicontrol {Tools > Options >
+    To select options for the Valgrind tools, select \uicontrol Tools >
-    Analyzer}. You can override the general settings for each project in the
+    \uicontrol Options > \uicontrol Analyzer. You can override the general
-    \uicontrol {Run Settings} for the project.
+    settings for each project in the \uicontrol {Run Settings} for the project.
 
     The following sections describe how to use the Valgrind tools:
 
@@ -74,4 +74,3 @@
     \endlist
 
 */
-

doc/qtcreator/src/analyze/creator-valgrind.qdoc

@@ -93,8 +93,9 @@
 
     Stack traces can get quite large and confusing, and therefore, reading them
     from the bottom up can help. If the stack trace is not big enough or it is
-    too big, select \uicontrol {Tools > Options > Analyzer} and define the
+    too big, select \uicontrol Tools > \uicontrol Options > \uicontrol Analyzer
-    length of the stack trace in the \uicontrol {Backtrace frame count} field.
+    and define the length of the stack trace in the
+    \uicontrol {Backtrace frame count} field.
 
     \image qtcreator-valgrind-memcheck-options.png "Memory Analysis options"
 
@@ -138,7 +139,6 @@
 
 */
 
-
 /*!
     \contentspage index.html
     \previouspage creator-analyzer.html
@@ -221,8 +221,9 @@
     separately for each project in the \l{Specifying Run Settings}{run settings}
     of the project.
 
-    To specify settings for Valgrind, select \uicontrol {Tools > Options >
+    To specify settings for Valgrind, select \uicontrol Tools >
-    Analyzer}. The \uicontrol {Profiling Options} group contains Callgrind options.
+    \uicontrol Options > \uicontrol Analyzer. The \uicontrol {Profiling Options}
+    group contains Callgrind options.
 
     \image qtcreator-valgrind-callgrind-options.png "Valgrind options"
 
@@ -269,7 +270,6 @@
 
 */
 
-
 /*!
     \contentspage index.html
     \previouspage creator-cache-profiler.html

doc/qtcreator/src/android/androiddev.qdoc

@@ -36,50 +36,42 @@
 
     \title Connecting Android Devices
 
-    You can connect Android devices to the development PC to run, debug,
+    You can connect Android devices to the development PC to build, run, debug,
-    and analyze applications built for them from \QC. Devices with Android
+    and analyze applications from \QC. Devices with Android
     version 4.1 (API level 16) or later are supported.
 
     If you have a tool chain for building applications for Android devices
     installed on the development PC, you can add it to \QC. You can then add a
     \l{glossary-buildandrun-kit}{kit}
-    with the Android device type, the tool chain, and the Qt version for Android,
+    with the tool chain, and the Qt version for Android for the device's architecture,
-    to build applications for and run them on Android devices. You can also
+    to build applications for and run them on Android devices. Starting from Qt 5.14.0,
-    allow \QC to automatically configure the kit.
+    Qt for Android package contains all the architectures (ABIs) installed as one.
+    You can also allow \QC to automatically create kits for installed Qt version
+    and tool chains.
 
     The Android Debug Bridge (adb) command line tool is integrated to \QC to
     enable you to deploy applications to connected Android devices, to run
-    the applications on them, and to read logs from them. It includes a client
+    them, and to read their logs. It includes a client and server that run on
-    and server that run on the development host and a daemon that runs on the
+    the development host and a daemon that runs on the emulator or device.
-    emulator or device.
 
     \section1 Requirements
 
     To use \QC to develop Qt applications for Android, you need the following:
 
     \list
-
+        \li \l{https://www.oracle.com/java/technologies/javase-jdk8-downloads.html}
-        \li \l{http://www.oracle.com/technetwork/java/javase/downloads/index.html}
+            {Java SE Development Kit (JDK)} version 6 up to 8.
-            {Java SE Development Kit (JDK)} version 6, or later.
             You can also use \l{http://openjdk.java.net/}{OpenJDK} on Linux.
 
             \note Android SDK Tools have issues with JDK versions later than 8.
 
         \li \l{http://www.gradle.org}{Gradle} for building application packages
             (APK) and app bundles (AAB) for Android devices. Gradle is delivered
-            with Qt 5.9, and later. Because Gradle scripts are not delivered
+            with Qt 5.9, and later, because Gradle scripts are not delivered
-            with  Android SDK tools since version 26.0.0, they are delivered
+            with  Android SDK tools since version 26.0.0.
-            with Qt 5.9 and 5.6.3.
 
             \note Using Ant to build APKs is no longer supported.
 
-        \li A tool chain for building applications for Android devices provided
-            by the \l{http://developer.android.com/tools/sdk/ndk/index.html}
-            {Android NDK} from Google.
-
-            \note To develop with Qt 5.14.0 or later, you need Android NDK r20
-            or later.
-
         \li \l{http://developer.android.com/sdk/index.html}{Android SDK Tools}
 
             The following Android SDK packages and tools are required for
@@ -89,47 +81,94 @@
                 \li Platform tools
                 \li Build tools
                 \li At least one SDK platform
+                \li The \l{http://developer.android.com/tools/sdk/ndk/index.html}
+                    {Android NDK} from Google that provides the tool chain for
+                    building applications for Android devices. For a detailed
+                    list of Qt versions and their recommended NDK versions,
+                    see \l{https://doc-snapshots.qt.io/qt5-5.14/android-getting-started.html}
+                    {The Android NDK}.
             \endlist
 
-        \li On Windows, you also need the following:
+            \li On Windows, you also need the Android Debug Bridge (ADB) driver
-
+                on the Windows platform to enable USB debugging. The default USB
-          \list
+                driver on Windows does not allow debugging. For more information
-
+                about installing ADB, see \l {ADB windows driver}
-            \li Android Debug Bridge (ADB) driver on the Windows platform to
+                {ADB driver installation}.
-                enable USB debugging. The default USB driver on Windows does not
-                allow debugging. For more information about obtaining the USB
-                driver, see \l{http://developer.android.com/sdk/win-usb.html}.
-
-                After installing the driver, try running a few basic
-                \l{http://developer.android.com/tools/help/adb.html}{adb}
-                commands to check that your device responds to them.
-
-          \endlist
-
-          \note When using the command line tools instead of Android Studio,
-                it is recommended to create an empty folder and extract the
-                downloaded archive into this folder.
-                The sdkmanager will install downloaded packages next to the
-                \c tools folder that contains all command line tools.
-                You must specify the path to the folder where you extracted the
-                files as Android SDK location inside the Android settings.
-
     \endlist
 
     \section1 Setting Up the Development Environment
 
-    You must download and install the latest Android NDK and SDK, and then
+    To build Android applications with Qt, install Qt for Android 5.2, or later.
-    update or install the tools and packages needed for development. However,
-    if your Qt version is earlier than v5.9, use the SDK tools package v25.2.5
-    or earlier.
 
-    The SDK tool used to update and install the other SDK tools and packages
+    \note You can build a 64-bit version of Qt for Android yourself. However,
-    depends on the Android SDK Tools version that you have installed:
+    for such a Qt version, the minimum required Android version on devices
+    is 5.0 (API level 21).
+
+    For more information, see \l{Qt for Android}.
+
+    Download and install the latest Android SDK, and then install
+    or update the NDKs, tools and packages needed for development.
+
+    Starting from \QC 4.12, \QC offers to automatically set up your Android
+    environment and install all the necessary packages and Tools, then
+    creating debuggers, tool chains, and kits. For more information,
+    see \l {Specifying Android Device Settings}.
+
+    Alternatively, use the Android SDK command line tools to install
+    the required packages. In that case, it is recommended to create an
+    empty folder and extract the downloaded archive into this folder.
+
+    \note The recommended Android SDK Tools version is 25.3.0, or later. The version
+    25.2.5, or earlier, can be used but it is not advised because it cannot be
+    fully integrated with \QC.
 
     \list
+        \li Android SDK Tools version 25.3.0, or later
+
+            This allows using the
+            \l{https://developer.android.com/studio/command-line/sdkmanager.html}
+            {sdkmanager} command line tool for SDK package management and the
+            \l{https://developer.android.com/studio/command-line/avdmanager.html}
+            {avdmanager} tool for Android Virtual Device (AVD) management.
+
+            The sdkmanager will install downloaded packages next to the \c tools
+            folder that contains all command line tools. You must specify the path
+            to the folder where you extracted the files as Android SDK location
+            inside the Android settings.
+
+            To install those packages, use the following command:
+
+            \badcode
+            ./sdkmanager "platform-tools" "platforms;android-29" "build-tools;29.0.2" "ndk-bundle"
+            \endcode
+
+            For Qt 5.12.0 to 5.12.5 and Qt 5.13.0 to 5.13.1, the following
+            should be installed instead:
+
+            \badcode
+            ./sdkmanager "platform-tools" "platforms;android-29" "build-tools;28.0.2" "ndk;19.2.5345600"
+            \endcode
+
+            \target ADB windows driver
+            Under Windows, Google's USB drivers can be installed by running:
+
+            \badcode
+            sdkmanager.bat "extras;google;usb_driver"
+            \endcode
+
+            For more information about altenative methods of obtaining the USB
+            driver, see \l{http://developer.android.com/sdk/win-usb.html}.
+            After the package installation is complete, install the driver from
+            \c{<ANDROID_SDK_ROOT>/extras/google/usb_driver}. Try running a few basic
+            \l{http://developer.android.com/tools/help/adb.html}{adb} commands now
+            and check whether your Android device responds to them.
 
         \li Android SDK Tools version 25.2.5, or earlier
 
+            If your Qt version is earlier than v5.9, use this SDK tools version.
+            The SDK tool used to install and update the other SDK tools and packages
+            depends on the Android SDK Tools version that you have installed:
+
             Use the
             \l{https://developer.android.com/studio/tools/help/android.html}
             {android} tool that comes with the SDK Tools package. For example,
@@ -139,61 +178,105 @@
             ./android update sdk
             \endcode
 
-        \li Android SDK Tools version 25.3.0, or later
-
-            Use the
-            \l{https://developer.android.com/studio/command-line/sdkmanager.html}
-            {sdkmanager} command line tool for SDK package management and the
-            \l{https://developer.android.com/studio/command-line/avdmanager.html}
-            {avdmanager} tool for Android Virtual Device (AVD) management.
-
     \endlist
 
-    In addition, you must install Qt for Android as part of Qt 5.2, or later.
-
-    \note You can build a 64-bit version of Qt for Android yourself. However,
-    for such a Qt version, the minimum required Android version on devices
-    is 5.0 (API level 21).
-
-    For more information, see \l{Qt for Android}.
-
     \section2 Specifying Android Device Settings
 
-    To configure connections between \QC and Android devices:
+    To configure connections to Android devices and general Android settings:
 
     \list 1
 
         \li Select \uicontrol Tools > \uicontrol Options > \uicontrol Devices >
             \uicontrol Android.
 
-            \image qtcreator-options-android1.png "Android options"
+            \image qtcreator-options-android-main.png "Android options"
 
-        \li In the \uicontrol {JDK location} field, add the path to the JDK.
+        \li In the \uicontrol {JDK location} field, set the path to the JDK.
 
-            Select the \inlineimage icons/download-icon.png
+            By default, \QC tries to find any valid JDK/OpenJDK installation.
-            (\uicontrol Download) button to go to the site where you can
+            However, if none is found, you must set it manually. Click the
-            download the JDK. \QC checks the JDK installation and reports
+            \inlineimage icons/download-icon.png
-            errors.
+            (\uicontrol Download) button to open the JDK download web page in the
+            default browser. \QC checks the JDK installation and reports errors.
 
-        \li In the \uicontrol {Android Settings} group, add paths to the Android
+        \li In the \uicontrol {Android Settings} group, set the path to the
-            NDK and SDK.
+            Android SDK Tools.
 
-            Select \inlineimage icons/download-icon.png
+            Select \inlineimage reload_gray.png
-            to go to the sites where you can download the Android NDK and SDK.
+            button to automatically download and extract the Android SDK Tools
+            to the selected path. This will do the following:
+
+            \list 1
+                \li Download and extract the Android SDK Tools.
+                \li Install or update the essential packages such as NDKs,
+                    build tools, platform tools.
+            \endlist
+
+            The SDK Tools download URL, the essential packages list, and the
+            appropriate NDK for each Qt version are defined in a JSON
+            configuration file. The file is located under the user's \QC
+            resource folder:
+
+            \badcode
+            # Linux and macOS
+            ~/.config/QtProject/qtcreator/android/sdk_definitions.json
+
+            # Windows
+            C:\Users\Username\AppData\Local\QtProject\qtcreator\android\sdk_definitions.json
+            \endcode
+
+            For example, the SDK configuration file defines the NDK version 19.2.5345600
+            to be used for Qt 5.12.0 to 5.12.5 and Qt 5.13.0 to 5.13.1 versions:
+
+            \badcode
+            "specific_qt_versions": [
+                {
+                    "versions": ["5.12.[0-5]", "5.13.[0-1]"],
+                    "sdk_essential_packages": ["build-tools;28.0.2", "ndk;19.2.5345600"],
+                    "ndk_path": "ndk/19.2.5345600"
+                }
+            ]
+            \endcode
+
+            The latest version of the configuration file that is up-to-date
+            with the Android SDK and NDK changes is found
+            \l{https://code.qt.io/cgit/qt-creator/qt-creator.git/plain/share/qtcreator/android/sdk_definitions.json}{here}.
+
+            The installed NDK versions are listed below the SDK path.
+            The items with a lock icon are versions installed from the SDK Manager,
+            and can only be modified from the SDK Manager tab. For more information,
+            see \l{Managing Android SDK Packages}. Custom NDK paths can be manually
+            added to the global list of NDKs via the \uicontrol Add button.
+            This creates custom tool chains and debuggers associated to
+            that NDK, which can be used to create custom kits defined by the user.
+
+            To manually download the SDK Tools, select \inlineimage icons/download-icon.png
+            to open the SDK or NDK download web page in the default browser.
 
             The SDK Manager checks the Android NDK and SDK installations,
             reports errors, and offers to install the necessary packages.
 
-            \image qtcreator-options-android2.png "Android NDK and SDK checks"
+            \image qtcreator-options-android-sdk-tools.png "Android NDK and SDK checks"
 
-            For more information, see \l {Managing Android SDK Packages}.
+        \li In the \uicontrol {Android OpenSSL} group, set the path to the
+            prebuilt OpenSSL libraries.
+
+            For Qt applications that require OpenSSL support, \QC allows to
+            quickly add the \l{https://marketplace.qt.io/products/android-openssl-support}
+            {Android OpenSSL support} to your project. For more details, see
+            \l{Adding External Libraries}.
+
+            Select \inlineimage icons/download-icon.png
+            to download the OpenSSL repository to the selected path. If the
+            automatic download fails, the download web page opens for manual download.
 
         \li Select the \uicontrol {Automatically create kits for Android tool chains}
             check box to allow \QC to create the kits for you. \QC displays a
             warning if it cannot find a suitable Qt version.
 
-        \li Select \uicontrol File > \uicontrol {New File or Project} > \uicontrol Application >
+        \li Select \uicontrol File > \uicontrol {New File or Project} >
-            \uicontrol {Qt Quick Application} > \uicontrol Choose, and
+            \uicontrol {Application (Qt Quick)} >
+            \uicontrol {Qt Quick Application - Empty} > \uicontrol Choose, and
             follow the instructions of the wizard to create a project. For more
             information, see
             \if defined(qtcreator)
@@ -213,12 +296,13 @@
             Debugging is enabled in different ways on different Android devices.
             Look for \uicontrol {USB Debugging} under \uicontrol {Developer Options}. On
             some devices \uicontrol {Developer Options} is hidden and becomes visible
-            when you tap the \uicontrol {Build number} field in \uicontrol Settings >
+            only when you tap the \uicontrol {Build number} field in \uicontrol Settings >
-            \uicontrol About several times.
+            \uicontrol About several times. For more details, check
+            \l{https://developer.android.com/studio/debug/dev-options}{Configure on-device developer options}.
 
         \li Connect the Android device to the development PC with a USB cable.
             You might be asked to select a device in the
-            \uicontrol {Select Android Devices} dialog.
+            \l{Selecting Android Devices}{Select Android Devices} dialog.
     \endlist
 
     \section2 Managing Android SDK Packages
@@ -230,11 +314,12 @@
     removing SDK packages. You can still use sdkmanager for advanced SDK
     management.
 
-    When you add paths to the Anroid NDK and SDK in the device options, the
+    After you set the path to the Anroid SDK in \uicontrol Tools >
+    \uicontrol Options > \uicontrol Devices > \uicontrol Android, the
     SDK Manager checks that all the necessary SDK packages have been installed.
     If packages are missing or updates are needed, the SDK Manager offers to
-    add and remove packages, as necessary. Before taking action, it prompts you
+    add or remove those packages. Before taking action, it prompts
-    to accept the changes it is about to make. In addition, it prompts you to
+    you to accept the changes it is about to make. In addition, it prompts you to
     accept Google licenses, as necessary.
 
     To view the installed Android SDK packages, select \uicontrol Tools >
@@ -261,13 +346,40 @@
     different Android SDK Tools versions. If you have the native SDK Manager
     installed, you can open it by selecting \uicontrol {Native SDK Manager}.
 
+    \section1 Managing Android Virtual Devices (AVD)
+
+    A list of AVDs is shown under \uicontrol Tools > \uicontrol Options >
+    \uicontrol Devices > \uicontrol Android > \uicontrol {AVD Manager}. This
+    works only with a valid \uicontrol {SDK Tools} path being set. The value in
+    \uicontrol {System/data partition size} is used to set the emulator's system
+    partition size upon execution with \uicontrol {Start}.
+
+    \image qtcreator-android-avd-manager.png "Android NDK and SDK checks"
+
+    \section1 Creating a New AVD
+
+    To create new virtual devices, select \uicontrol Tools > \uicontrol Options >
+    \uicontrol Devices > \uicontrol Android > \uicontrol {AVD Manager} > \uicontrol {Add}.
+
+    In the \uicontrol {Create new AVD} dialog, you can create a new custom AVD
+    by setting the name, device type, skin, architecture, API level, and SD card
+    size. You need to have a valid \uicontrol {System Image} installed
+    before using this dialog, either from \QC's \uicontrol {SDK Manager} tab or
+    from Android Studio.
+
+    For more advanced options for creating a new AVD, use the command-line tool
+    \l{https://developer.android.com/studio/command-line/avdmanager.html}{avdmanager},
+    or use Android Studio's native AVD Manager's UI.
+
+    \image qtcreator-android-create-avd.png "Android NDK and SDK checks"
+
     \section1 Selecting Android Devices
 
     When you deploy an application to an Android device with Android
-    version 4.2 or later, the \uicontrol {Select Android Devices} dialog opens. It
+    version 4.2 (API 16) or later, the \uicontrol {Select Android Device} dialog
-    lists the devices that are connected to the development PC. and their
+    opens. It lists the devices that are connected to the development PC, as
-    status. You can select devices from the \uicontrol {Compatible Devices} list for
+    well as AVDs, and their status. You can select devices or AVDs from the
-    deployment.
+    \uicontrol {Compatible Devices} list for deployment.
 
     If \QC determines that a device is not ready for deployment, it places the
     device in the \uicontrol {Incompatible Devices} list, with information about the
@@ -276,34 +388,41 @@
     \uicontrol {Refresh Device List}. The device is moved to the
     \uicontrol {Compatible Devices} list and you can select it for deployment.
 
-    Other reasons for placing a device on the \uicontrol {Incompatible Devices} are
+    Other reasons for showing a device in \uicontrol {Incompatible Devices} are
     that the Android version on the device is too old or that the tool chain
     used for building does not match the Android architecture on the device
     (for example, you cannot deploy an ARM build on an x86 device).
 
     \image qtcreator-android-select-devices.png "Select Android Devices dialog"
 
-    AVDs are also listed. To create new AVDs, select
+    To \l{Creating a New AVD}{create a new AVD}, select \uicontrol {Create Android Virtual Device}.
-    \uicontrol {Create Android Virtual Device}.
 
-    To set a device as the default device for a particular Android architecture,
+    To set a device as the default device for a particular Android architecture
-    select the \uicontrol {Always use this device for architecture} check box. The
+    for the current project, select the \uicontrol {Always use this device for architecture}
-    \uicontrol {Select Android Devices} dialog will not appear until you switch to
+    check box. The \uicontrol {Select Android Devices} dialog will not appear
-    another project or restart \QC.
+    until you switch to another project or restart \QC.
 
     \section1 Using the Android Emulator
 
-    To run your application on the Android Emulator, you must create Android
+    To run your application on the Android Emulator, you must have an Android
-    virtual devices (AVD). Select \uicontrol Tools > \uicontrol Options >
+    virtual device (AVD). For more information about creating a new one, see
-    \uicontrol Devices > \uicontrol Android >
+    \l{Creating a New AVD}. If you run an application without a device connected to the
-    \uicontrol Add. If you run an application without a device connected to the
     development PC and without an AVD specified, \QC asks you to add an AVD.
 
-    To manage AVDs, select \uicontrol {Start AVD Manager}.
+    For Android SDK Tools 25.2.5, or earlier, select \uicontrol {Native AVD Manager}
+    to manage AVDs.
 
     \note The Android Emulator has a bug that prevents it from starting on some
     systems. If the Android Emulator does not start, you can try starting it
-    manually by running the \c {emulator-arm} command from the command line.
+    manually by running the following commands:
+
+    \badcode
+    cd <ANDROID_SDK>/emulator
+    ./emulator -avd <AVD_NAME>
+    \endcode
+
+    For more information, see \l{https://developer.android.com/studio/run/emulator-commandline}
+    {Start the emulator from the command line}.
 
     \section1 Debugging on Android Devices
 
@@ -312,6 +431,9 @@
 
     \note \QC cannot debug applications on Android devices if Android Studio is
     running. If the following message is displayed in the \uicontrol Output
-    pane, close Android Studio and try again: \e {Ignoring second debugger -
+    pane, close Android Studio and try again:
-    accepting and dropping.}
+
+    \badcode
+    Ignoring second debugger -accepting and dropping.
+    \endcode
 */

doc/qtcreator/src/android/creator-projects-settings-run-android.qdocinc

@@ -37,6 +37,18 @@
     \uicontrol {Activity manager start options} field. However, if the default
     options conflict with the added options, the application might not start.
 
+    The default arguments for the Activity manager for a normal run:
+
+    \badcode
+    am start -n org.qtproject.example.notification/org.qtproject.qt5.android.bindings.QtActivity
+    \endcode
+
+    The default arguments for the Activity manager for the debugger mode:
+
+    \badcode
+    am start -n org.qtproject.example.notification/org.qtproject.qt5.android.bindings.QtActivity -D
+    \endcode
+
     For example, to run the application as a particular user, enter the start
     option \c {--user 10}, where \c 10 is the user ID of the user account.
 

doc/qtcreator/src/android/deploying-android.qdoc

@@ -47,18 +47,13 @@
     \QC supports the following methods of deployment for Android applications:
 
     \list
-
         \li As a stand-alone, distributable application package (APK).
-
-        \li As a minimal APK that contains a dependency to the Ministro tool.
-            The Ministro tool downloads the necessary Qt libraries from a
-            repository of your choice.
-
         \li Since Qt 5.14.0, as an app bundle (AAB), intended for distribution
             in the Google Play store.
-
     \endlist
 
+    \note Since \QC 4.12, Ministro is not supported.
+
     To specify settings for application packages, select \uicontrol Projects >
     \uicontrol {Build Android APK} > \uicontrol Details.
 
@@ -67,23 +62,6 @@
     see \l {Specifying Run Settings for Android Devices}.
     \endif
 
-    \section1 Using Ministro to Install Qt Libraries
-
-    To minimize the size of your APK, you can package the application with an
-    external dependency called Ministro. If a user downloads your application,
-    and it is the first application on their device to depend on Ministro, they
-    are asked to install Ministro before they can run your application.
-
-    Ministro serves as a central repository for Qt libraries. This enables
-    several applications to share the libraries, which only need to be installed
-    once. To use this deployment method, you must set up a repository for the
-    libraries that you want to distribute. To specify the
-    repository URL, edit the file \c {android/res/values/libs.xml}, which is
-    created by \QC.
-
-    To use Ministro to install the Qt libraries, select the
-    \uicontrol {Use Ministro service to install Qt} option.
-
     \section1 Packaging Applications
 
     Because bundling applications as APK packages is not
@@ -126,8 +104,8 @@
 
     The packages are deployed on the connected Android devices. To switch the
     device used as a default device for the selected kit, select
-    \uicontrol Projects > \uicontrol Run >
+    \uicontrol Projects > \uicontrol Run > \uicontrol {Deploy to Android device}
-    \uicontrol {Reset Default Devices}. The setting applies until you restart \QC.
+    > \uicontrol {Reset Default Devices}. The setting applies until you restart \QC.
     For more information, see \l{Selecting Android Devices}.
 
     For more information about the \c androiddeployqt tool, see
@@ -137,7 +115,7 @@
 
     You can specify settings for the \c androiddeployqt tool in \QC and in the
     project .pro file. To specify settings in \QC, select \uicontrol Projects >
-    \uicontrol {Build Android APK} > \uicontrol Details.
+    \uicontrol Build > \uicontrol {Build Android APK} > \uicontrol Details.
 
     \image qtcreator-android-deploy-configurations.png "Deploy configurations"
 
@@ -150,6 +128,22 @@
     the \uicontrol {Compile Output} pane. To view additional information, select the
     \uicontrol {Verbose output} check box.
 
+    \section3 Selecting API Level
+
+    In the \uicontrol {Android build SDK} field, you can select the API level to use
+    for building the application. Usually, you should select the newest API
+    level available.
+
+    \note For Qt 5.12.0 to 5.12.5 and Qt 5.13.0 to 5.13.1, Android build SDK 28 should
+    be used. For recent versions than the latter, build SDK 29, or the most recent
+    should be used.
+
+    This field does not specify the minimum supported API level nor the target
+    API level, which you can specify in the Android manifest. See
+    \l{Editing Manifest Files}. For more information about Android API levels, see
+    \l{http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels}
+    {What is API Level?}.
+
     \section3 Building AABs
 
     For testing the application locally, use the APK format, because
@@ -167,18 +161,6 @@
 
     \image qtcreator-android-build-steps.png "Android Build Steps"
 
-    \section3 Selecting API Level
-
-    In the \uicontrol {Android build SDK} field, you can select the API level to use
-    for building the application. Usually, you should select the newest API
-    level available.
-
-    This field does not specify the minimum supported API level nor the target
-    API level, which you can specify in the Android manifest file.
-    For more information about Android API levels, see
-    \l{http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels}
-    {What is API Level?}.
-
     \section3 Signing Android Packages
 
     To publish your application, you must sign it by using a \e {public-private
@@ -211,9 +193,9 @@
 
     \list 1
 
-        \li In the \uicontrol Keystore field, select \uicontrol Create to create a new
+        \li In the \uicontrol Keystore field, select \uicontrol Create to create
-            keystore that contains one key pair in the \uicontrol {Create Keystore and
+            a new keystore that contains one key pair in the
-            a Certificate} dialog:
+            \uicontrol {Create a Keystore and a Certificate} dialog:
 
             \image qtcreator-android-certificate.png
 
@@ -238,8 +220,8 @@
 
     \endlist
 
-    To sign an Android package by using a key pair, specify settings in the
+    To sign an Android package by using a key pair, set the \uicontrol {Sign package}
-    \uicontrol {Sign package} group:
+    group settings described in \l{Specifying Settings for Packages}:
 
     \list 1
 
@@ -258,21 +240,29 @@
 
     \QC automatically detects which Qt libraries the application uses and adds
     them as dependencies. If the application needs external libraries, specify
-    them in the \uicontrol {Additional Libraries} field. The libraries are copied into
+    them in \uicontrol Projects > \uicontrol Build > \uicontrol {Build Android APK}
+    > \uicontrol {Additional Libraries} field. The libraries are copied into
     your application's library folder and loaded on startup.
 
-    For example, to enable OpenSSL in your application, add the paths to the
+    To add OpenSSL libraries, select \uicontrol {Include prebuilt OpenSSL libraries}
-    required \c libssl.so and \c libcrypto.so libraries to the
+    in the \uicontrol {Additional Libraries} group. This will add the OpenSSL
-    \uicontrol {Additional Libraries} field.
+    include project defined in \l{Specifying Android Device Settings}{device settings}
+    in \uicontrol {Android OpenSSL} group. This can be used for QMake and CMake
+    projects.
 
-    \section3 Editing Manifest Files
+    Otherwise, you can manually add the paths to the required \c libssl.so and
+    \c libcrypto.so libraries to the \uicontrol {Additional Libraries} field.
+
+    \section1 Editing Manifest Files
 
     You can use the qmake variables to specify all
     the settings you need for the \c androiddeployqt tool and you do not need an
-    Android manifest file until you want to publish the package in an
+    Android manifest file unless you need to specify Android specific settings
-    application store. To specify additional settings for APK packages, you can
+    like the application's icon. Also, the manifest file is needed if you want
-    create an Android manifest file and edit it in \QC. Select
+    to publish the package in the Play Store.
-    \uicontrol {Create Templates} to create the file and to open it in the
+    You can create an Android manifest file and edit it in \QC. Select
+    \uicontrol Projects > \uicontrol Build > \uicontrol {Build Android APK}
+    > \uicontrol {Create Templates} to create the file and to open it in the
     Android Manifest Editor.
 
     \image qtcreator-android-manifest-editor.png "Android Manifest Editor"
@@ -292,9 +282,10 @@
     field, specify the version number that is shown to users.
 
     \li In the \uicontrol {Minimum required SDK} field, select the minimum API level
-    required to run the application. The minimum supported API level is
+    required to run the application. The minimum supported API level for \QC is
-    android-9. \QC does not allow you to select an API
+    android-9. However, Qt versions might have different minimum API levels, and
-    level that the Qt version specified for the kit does not support.
+    therefore \QC does not allow you to select an API level that the Qt version
+    specified for the kit does not support.
 
     \li In the \uicontrol {Target SDK} field, select the targeted API level of the
     application. This affects the activation of some compatibility features in
@@ -302,42 +293,49 @@
     means that the overflow button in the system navigation bar will not be
     enabled by default.
 
-    \li In the \uicontrol Application group, you can give the application a name and
+    \li In the \uicontrol Application group, you can set the application's name.
-    select an icon for it. The three icon fields can contain different versions
-    of the icon with low, medium, and high DPI values, from left to right.
         You can also give an activity a name and select the activity to run.
 
+    \li The \uicontrol {Style extraction} combo box sets the used method that Qt
+        uses to extract style information. It has the following values:
+        \list
+            \li \uicontrol Default or \uicontrol Full: Use this when working with
+                Qt Widgets or Qt Quick Controls 1.
+
+                \note This method uses some Android non-SDK interfaces,
+                      that are being restricted by Google starting from Android 9.0
+                      (API 28).
+            \li \uicontrol minimal: Use this when working with Qt Quick Controls 2
+                with no Qt Widgets or Qt Quick Controls 1. This is faster than
+                \uicontrol full or \uicontrol default.
+            \li \uicontrol none: Use this if you're not working with Qt Widgets,
+                or Qt Quick Controls 1 or 2 in your project.
+        \endlist
+
+    \li In \uicontrol {Application icon}, select an icon. Click the
+    \uicontrol {Master icon} button to select an icon with the highest resolution,
+    then, it will resize and set the three icon fields for low, medium, and high DPI icons
+    as needed.
+
     \li In the \uicontrol Permissions field, you can specify the permissions that your
-    application needs. Users are asked to grant the permissions when they
+    application needs. Starting from Android 6.0 (API 23), permissions have to be
-    install the application. Android OS then grants the application access to
+    requested at runtime (See \l{QtAndroidExtras}{requestPermissionsSync} or
-    the appropriate data and features.
+    \l{QtAndroidExtras}{requestPermissions}). For lower Android API levels,
+    users are asked to grant the permissions when they install the application.
+    Android OS then grants the application access to the appropriate data and features.
 
     \li Select the \uicontrol {Include default permissions for Qt modules} and
     \uicontrol {Include default features for Qt modules} check boxes to add the
-    permissions needed by Qt libraries.
+    permissions needed by Qt libraries. This can be
+    android.permission.WRITE_EXTERNAL_STORAGE for QtCore, or
+    android.permission.ACCESS_COARSE_LOCATION for QtLocation.
 
-    \li To add permissions, select them in the list, and then select \uicontrol Add.
+    \li To add a permission, select it from the list, and then click \uicontrol Add.
 
     \endlist
 
-    Select the \uicontrol {XML Source} tab to edit the file in XML format.
+    On the top header, select the \uicontrol {XML Source} tab to edit the file
-
+    in XML format.
-    \section1 Installing Ministro
-
-    The easiest way to install Ministro is to do it on the device via Google
-    Play. When you run the application for the first time, a dialog pops up and
-    guides you through the installation.
-
-    To use \QC to install Ministro, you must first download the Ministro .apk
-    from the Google Market or from the
-    \l{http://necessitas.kde.org/necessitas/ministro.php}{Ministro} home page.
-
-    Then select \uicontrol Projects > \uicontrol Run > \uicontrol {Install Ministro from APK}.
-
-    You can use this option also to install any Android package (.apk).
-
-    You can use this option to install applications on an Android Virtual
-    Device (AVD).
 
 */
 

doc/qtcreator/src/debugger/creator-only/creator-debugger.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2019 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -380,6 +380,11 @@
             debugger at the main function.
         \li In the \uicontrol {Server start script} field, specify a
             script file to run when the server starts.
+        \li In the \uicontrol {Init commands} field, enter the commands
+            to execute immediately after the connection to a target has
+            been established.
+        \li In the \uicontrol {Reset commands} field, enter the commands
+            to execute when resetting the connection to a target.
         \li In the \uicontrol {Debug information} field, specify the location
             for storing debug information. You cannot use an empty path.
         \li In the \uicontrol {Override server channel} field, specify a
@@ -620,6 +625,9 @@
     To save space on the screen, select \uicontrol Window > \uicontrol Views >
     \uicontrol {Automatically Hide View Titlebars}.
 
+    To show and hide columns in views, toggle \uicontrol {Show Column} in
+    the context menu.
+
     Once the program starts running under the control of the debugger, it
     behaves and performs as usual. You can interrupt a running C++ program by
     selecting \uicontrol Debug > \uicontrol Interrupt. The program is

doc/qtcreator/src/debugger/qtquick-debugging.qdoc

@@ -79,8 +79,8 @@
             the \uicontrol {Enable QML} check box to enable
             QML debugging.
 
-        \li Select \uicontrol {Build > Rebuild Project} to clean and rebuild the
+        \li Select \uicontrol Build > \uicontrol {Rebuild Project} to clean and
-            project.
+            rebuild the project.
 
         \li To debug applications on \l{glossary-device}{devices}, check that
             Qt 5.0, or later, libraries are installed on the device and
@@ -144,7 +144,8 @@
             the application from running until the debug client connects to the
             server. This enables debugging from the start.
 
-        \li Select \uicontrol {Debug > Start Debugging > Attach to QML Port}.
+        \li Select \uicontrol Debug > \uicontrol {Start Debugging} >
+            \uicontrol {Attach to QML Port}.
 
             Choose the kit configured for the device where the application to
             be debugged is running. The port number to use is displayed in the

doc/qtcreator/src/editors/creator-editors-options-text.qdoc

@@ -42,7 +42,8 @@
     \title Specifying Text Editor Settings
 
     Set the font preferences and apply color schemes for syntax highlighting in
-    \uicontrol {Tools > Options > Text Editor > Font & Colors}.
+    \uicontrol Tools > \uicontrol Options > \uicontrol {Text Editor} >
+    \uicontrol {Font & Colors}.
 
     \image qtcreator-font-colors.png "Text editor options"
 

doc/qtcreator/src/editors/creator-only/creator-mime-types.qdoc

@@ -69,7 +69,8 @@
 
     \list 1
 
-        \li Select \uicontrol {Tools > Options > Environment > MIME Types}.
+        \li Select \uicontrol Tools > \uicontrol Options >
+            \uicontrol Environment > \uicontrol {MIME Types}.
 
             \image qtcreator-mime-types.png "MIME Types"
 

doc/qtcreator/src/external-resources/external-resources.qdoc

@@ -34,3 +34,24 @@
     \title macOS
     \internal
 */
+
+/*!
+    \externalpage https://doc.qt.io/QtForMCUs/qtul-environment.html
+    \title Qt for MCUs - Supported Target Platforms
+*/
+/*!
+    \externalpage https://doc.qt.io/QtForMCUs/qtul-getting-started-on-stm.html
+    \title Getting Started on STM
+*/
+/*!
+    \externalpage https://doc.qt.io/QtForMCUs/qtul-getting-started-on-stm.html
+    \title Getting Started on STM
+*/
+/*!
+    \externalpage https://doc.qt.io/QtForMCUs/qtul-getting-started-on-nxp.html
+    \title Getting Started on NXP
+*/
+/*!
+    \externalpage https://doc.qt.io/QtForMCUs/qtul-getting-started-windows.html
+    \title Getting Started on Windows
+*/

doc/qtcreator/src/howto/creator-external-tools.qdoc

@@ -70,8 +70,8 @@
     \uicontrol Linguist > \uicontrol {Release Translations (lrelease)}.
 
     By default, the project .pro file is passed to the tools as an argument. To
-    specify other command line arguments for the tools, select \uicontrol {Tools >
+    specify other command line arguments for the tools, select \uicontrol Tools >
-    External > Configure}.
+    \uicontrol External > \uicontrol Configure}.
 
     To open TS files in Qt Linguist, right-click a TS file in the
     \uicontrol Projects or \uicontrol {File System} view and select
@@ -111,9 +111,10 @@
 
     \list 1
 
-        \li Select \uicontrol {Tools > External > Configure}.
+        \li Select \uicontrol Tools > \uicontrol External >
+            \uicontrol Configure.
 
-        \li Select \uicontrol {Add > Add Tool}
+        \li Select \uicontrol Add > \uicontrol {Add Tool}
             to add a new tool. You can also select \uicontrol {Add Category} to add a
             new category.
 
@@ -163,7 +164,8 @@
 
     \endlist
 
-    The category and tool are added to the \uicontrol {Tools > External} menu.
+    The category and tool are added to the \uicontrol Tools >
+    \uicontrol External menu.
 
     If you change the configuration of preconfigured tools, you can later
     revert the changes by selecting the \uicontrol Reset button.

doc/qtcreator/src/howto/creator-help.qdoc

@@ -78,11 +78,11 @@
 
     \section1 Viewing Function Tooltips
 
-    To hide function tooltips by default, select \uicontrol {Tools > Options >
+    To hide function tooltips by default, select \uicontrol Tools >
-    Text Editor > Behavior > Show help tooltips using the mouse >
+    \uicontrol Options > \uicontrol {Text Editor} > \uicontrol Behavior >
-    On Shift+Mouseover}. You
+    \uicontrol {Show help tooltips using the mouse} >
-    can still view the tooltips by pressing and holding down the \key Shift
+    \uicontrol {On Shift+Mouseover}. You can still view the tooltips by pressing
-    key.
+    and holding down the \key Shift key.
 
     To use a keyboard shortcut for viewing help tooltips, select
     \uicontrol {Show help tooltips using keyboard shortcut (Alt)}.
@@ -256,7 +256,8 @@
 
     \list 1
 
-        \li Select \uicontrol {Tools > Options > Help > Filters > Add}.
+        \li Select \uicontrol Tools > \uicontrol Options > \uicontrol Help >
+            \uicontrol Filters > \uicontrol Add.
 
         \li Enter a name for the filter and press \uicontrol {OK}.
 

doc/qtcreator/src/howto/creator-keyboard-shortcuts.qdoc

@@ -50,8 +50,8 @@
 
     To view all functions available in \QC and the keyboard shortcuts defined
     for them, select
-    \uicontrol {Tools > Options > Environment > Keyboard}. The shortcuts are listed by
+    \uicontrol Tools > \uicontrol Options > \uicontrol Environment >
-    category. To find a keyboard
+    \uicontrol Keyboard. The shortcuts are listed by category. To find a keyboard
     shortcut in the list, enter a function name or shortcut in the \uicontrol Filter
     field.
 

doc/qtcreator/src/howto/creator-only/creator-how-tos.qdoc

@@ -255,7 +255,8 @@
     create your own locator filters. That way you can locate files in a
     directory structure you have defined.
 
-    To create locator filters, select \uicontrol {Tools > Options > Locator > Add}.
+    To create locator filters, select \uicontrol Tools > \uicontrol Options >
+    \uicontrol Locator > \uicontrol Add.
 
     For more information, see \l{Creating Locator Filters}.
 
@@ -275,9 +276,9 @@
     \section1 Add a license header template for C++ code
 
     A file containing a license header for C++ can be specified under
-    \uicontrol{Tools > Options > C++ > License Template}. It may contain special
+    \uicontrol Tools > \uicontrol Options > \uicontrol C++ >
-    placeholders enclosed in \c{%%} that are replaced when generating a
+    \uicontrol {License Template}. It may contain special placeholders enclosed
-    new file:
+    in \c{%%} that are replaced when generating a new file:
 
     \list 1
 

doc/qtcreator/src/howto/creator-only/creator-sessions.qdoc

@@ -39,7 +39,8 @@
 
     When you exit \QC, a snapshot of your current workspace is stored as a
     \e session. To restore the session automatically when you start \QC,
-    select \uicontrol {File > Sessions > Manage > Restore last session on startup}.
+    select \uicontrol File > \uicontrol Sessions > \uicontrol Manage >
+    \uicontrol {Restore last session on startup}.
 
     When you open or create any of the following items, they automatically
     become a part of the session:

doc/qtcreator/src/howto/creator-only/qtcreator-faq.qdoc

@@ -55,9 +55,9 @@
     compiler. What should I do?}
 
     Make sure that the application is in your system PATH when starting \QC.
-    Also select \uicontrol {Tools > Options} to check the settings specified
+    Also select \uicontrol Tools > \uicontrol Options to check the settings
-    for the application. Many plugins specify either the path to the tool they
+    specified for the application. Many plugins specify either the path to the
-    need or the environment they run in.
+    tool they need or the environment they run in.
 
     This is especially relevant for the \macos where \c {/usr/local/bin} might
     not be in the path when \QC is started.
@@ -66,9 +66,10 @@
 
     \QC has been localized into several languages. If the system
     language is one of the supported languages, it is automatically selected.
-    To change the language, select \uicontrol {Tools > Options > Environment} and
+    To change the language, select \uicontrol Tools > \uicontrol Options >
-    select a language in the \uicontrol Language field. Select
+    \uicontrol Environment and select a language in the \uicontrol Language
-    \uicontrol {Restart Now} to restart \QC and have the change take effect.
+    field. Select \uicontrol {Restart Now} to restart \QC and have the change
+    take effect.
 
     \b {Has a reported issue been addressed?}
 
@@ -172,8 +173,9 @@
     \uicontrol Help mode.
 
     To view the documentation that is available and to add documentation,
-    select \uicontrol {Tools > Options > Help > Documentation}. For more
+    select \uicontrol Tools > \uicontrol Options > \uicontrol Help >
-    information, see \l{Adding External Documentation}.
+    \uicontrol Documentation. For more information, see
+    \l{Adding External Documentation}.
 
     \section1 Debugger Questions
 
@@ -195,10 +197,11 @@
     \b {How do I generate a core file in \QC?}
 
     To trigger the GDB command that generates a core file while debugging,
-    select \uicontrol {Window > Views > Debugger Log}. In the \uicontrol Command field,
+    select \uicontrol Window > \uicontrol Views > \uicontrol {Debugger Log}.
-    type \c gcore and press \key Enter. The core file is created in the
+    In the \uicontrol Command field, type \c gcore and press \key Enter. The
-    current working directory. You can specify another location for the file,
+    core file is created in the current working directory. You can specify
-    including a relative or absolute path, as an argument of the command.
+    another location for the file, including a relative or absolute path, as an
+    argument of the command.
 
     \omit
     To generate a temporary core file, select \uicontrol {Create Snapshot} in the
@@ -272,8 +275,8 @@
     type of application, \c qDebug() and related functions use standard output
     and error output.
 
-    We recommend that you select \uicontrol {Projects > Run Settings > Run in
+    We recommend that you select \uicontrol Projects > \uicontrol {Run Settings} >
-    terminal} for console applications.
+    \uicontrol {Run in terminal} for console applications.
 
     For GUI applications, \c qDebug() and related functions use the Windows API
     function \c OutputDebugString(). The output is displayed in the

doc/qtcreator/src/howto/creator-ui.qdoc

@@ -386,7 +386,7 @@
     \else
     \l{Using Git}{Version Control}
     \endif
-     panes, select \uicontrol {Window > Output Panes}.
+     panes, select \uicontrol Window > \uicontrol {Output Panes}.
     \if defined(qtcreator)
     To display the \uicontrol {To-Do Entries} pane, enable the Todo plugin.
     \endif

doc/qtcreator/src/howto/creator-views.qdoc

@@ -120,7 +120,8 @@
             (\uicontrol {Filter Tree}) and select \uicontrol{Simplify Tree}.
 
         \li To hide source files which are automatically generated by the build
-            system, select \uicontrol {Filter Tree > Hide Generated Files}.
+            system, select \uicontrol {Filter Tree} >
+            \uicontrol {Hide Generated Files}.
 
         \li To hide source files which are not enabled for the current target,
             select \uicontrol {Filter Tree} > \uicontrol {Hide Disabled Files}.

doc/qtcreator/src/mcu/creator-mcu-dev.qdoc

@@ -47,22 +47,11 @@
     Linux, and macOS. However, the Qt for MCU SDK is currently only available
     for Windows.
 
-    The following MCU boards are currently supported:
+    For a list of Qt for MCU reference implementations, see the
-
+    \l{Qt for MCUs - Supported Target Platforms}{Qt for MCUs} documentation.
-    \list
-        \li \l{https://www.st.com/en/evaluation-tools/stm32f7508-dk.html}
-            {STM32F7508-DK}
-        \li \l{https://www.st.com/en/evaluation-tools/32f769idiscovery.html}
-            {STM32F769I-DISCO}
-        \li \l{https://www.nxp.com/design/development-boards/i.mx-evaluation-and-development-boards/i.mx-rt1050-evaluation-kit:MIMXRT1050-EVK}
-            {NXP i.MX RT1050 EVK}
-    \endlist
-
-    For a list of Qt for MCU reference implementations, see the Qt for MCU
-    documentation.
 
     You use the \l{Connecting Bare Metal Devices}{Bare metal plugin} to connect
-    to OpenOCD or ST-LINK Utility for debugging on MCUs.
+    to a debug server provider for debugging on MCUs.
 
     \section1 Requirements
 
@@ -73,25 +62,18 @@
         \li The Bare Metal plugin
         \li \l{https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm}
             {GNU ARM Embedded Toolchain}
-        \li For STM32 boards:
+        \li The hardware specific requirements vary depending on the hardware platform you are developing for.
+            For more information see:
             \list
-            \li \l{https://www.st.com/en/embedded-software/stm32cubef7.html}
+                \li \l{Getting Started on NXP}
-                {STM32Cube SDK}
+                \li \l{Getting Started on STM}
-            \li \l{https://www.st.com/en/development-tools/stm32cubeprog.html}
-                {STM32Cube Programmer}
-        \endlist
-        \li For NXP boards:
-        \list
-            \li \l{https://www.nxp.com/design/development-boards/i.mx-evaluation-and-development-boards/i.mx-rt1050-evaluation-kit:MIMXRT1050-EVK}
-                {NXP EVKB-IMXRT 1050 SDK}
-            \li \l{https://www.segger.com/downloads/jlink}{SEGGER JLink}
              \endlist
     \endlist
 
     \section1 Setting Up the Development Environment
 
     You must download and install the required software and create connections
-    between \QC and MCUs.
+    between \QC and MCUs. For more information, see \l{Getting Started on Windows}.
 
     \section2 Enabling Bare Metal and MCU Plugins
 
@@ -117,7 +99,10 @@
     \image qtcreator-mcu-options.png "MCU options"
 
     \list 1
-        \li In the \uicontrol {MCU board} field, select your MCU board.
+        \li In the \uicontrol {Qt for MCUs SDK} field, specify the path
+            to the directory where you installed Qt for MCUs SDK.
+        \li In the \uicontrol {Targets supported by the Qt for MCUs SDK}
+            field, select your MCU board.
         \li In the \uicontrol {GNU ARM Embedded Toolchain} field,
             specify the path to the directory where you installed the
             tool chain.
@@ -137,8 +122,6 @@
                 \li In the \uicontrol {SEGGER JLink} field, specify the
                     path to the directory where you installed the tool.
             \endlist
-        \li In the \uicontrol {Qt MCU SDK} field, specify the path to the
-            directory where you installed Qt MCU.
         \li Select \uicontrol Apply to save the settings and to generate
             a MCU device and kit.
     \endlist
@@ -193,8 +176,8 @@
 
     \list 1
         \li Select \uicontrol File > \uicontrol {New File or Project} >
-            \uicontrol Application > \uicontrol {MCU Support Application} >
+            \uicontrol {Application (Qt Quick)} >
-            \uicontrol Choose.
+            \uicontrol {MCU Support Application} > \uicontrol Choose.
         \li Follow the instructions of the wizard to create the project.
         \li Select \uicontrol Projects > \uicontrol {Build & Run}, and then
             select the kit for building the application and running it on the

doc/qtcreator/src/overview/creator-only/creator-getting-started.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2018 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -39,8 +39,8 @@
 
     \table
         \row
-            \li \inlineimage creator-gs-01.png
+            \li \inlineimage creator_gettingstarted.png
-            \li \inlineimage creator-gs-02.png
+            \li \inlineimage creator_designinguserinterface.png
             \li \inlineimage creator_advanceduse.png
         \row
             \li \b {\l{IDE Overview}}
@@ -60,8 +60,8 @@
                 control systems. For an overview of the options you have, go to
                 \l{Configuring Qt Creator}.
         \row
-            \li \inlineimage creator-gs-03.png
+            \li \inlineimage creator_buildingrunning.png
-            \li \inlineimage creator-gs-04.png
+            \li \inlineimage creator_gettinghelp.png
             \li
         \row
             \li \b {\l{Building and Running an Example}}

doc/qtcreator/src/overview/creator-only/creator-tutorials.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2019 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -37,7 +37,7 @@
 
     \title Tutorials
 
-    \image creator-gs-04.png
+    \image creator_gettinghelp.png
 
     You can use \QC to create applications for several platforms by using
     several technologies. The tutorials in this manual explain how to create

doc/qtcreator/src/projects/creator-only/creator-projects-building.qdoc

@@ -60,7 +60,8 @@
 
         \image qtcreator-kit-selector.png "Kit selector"
 
-        \li  Choose \uicontrol {Build > Build Project} or press \key {Ctrl+B}.
+        \li  Choose \uicontrol Build > \uicontrol {Build Project} or press
+             \key {Ctrl+B}.
 
              You can also select the \uicontrol Run button (2) to also deploy and run
              the application after building it.

doc/qtcreator/src/projects/creator-only/creator-projects-creating.qdoc

@@ -98,15 +98,9 @@
 
     \list
 
-        \li Applications
+        \li Application (Qt Quick)
 
         \list
-
-            \li Qt Widgets Application
-
-                Use \QD forms to design a Qt widget based user interface for the
-                desktop and C++ to implement the application logic
-
             \li Qt Quick Application - Empty
 
                 Create an empty Qt Quick application that uses Qt Quick 2 types.
@@ -121,10 +115,25 @@
                 {Qt Quick Controls} to implement a scrollable list (requires
                 Qt 5.9 or later) or a set of pages with a stack-based or
                 swipe-based navigation model (requires Qt 5.7 or later).
+        \endlist
+
+        \li Application (Qt)
+
+        \list
+
+            \li Qt Widgets Application
+
+                Use \QD forms to design a Qt widget based user interface for the
+                desktop and C++ to implement the application logic
 
             \li Qt Console Application
 
                 Use a single main.cpp file
+        \endlist
+
+        \li Application (Qt for Python)
+
+            \list
 
             \li Qt for Python Application - Empty, Window, Window (UI file), or
                 Qt Quick Application (Empty)
@@ -135,13 +144,17 @@
                 a widget-based UI. Alternatively, you can create an empty
                 Qt Quick Application.
 
+            \endlist
+
+        \li Application (Qt for MCU)
+
+            \list
                 \li MCU Support Application
 
                     Creates an application that uses a subset of QML and
                     Qt Quick Controls (as supported by Qt for MCUs) that
                     you can deploy, run, and debug on MCU boards. For more
                     information, see \l {Connecting MCUs}.
-
             \endlist
 
         \li Libraries
@@ -467,8 +480,9 @@
     subproject in the \uicontrol{Project Management} dialog. However, the root project
     must specify that qmake uses the \c subdirs template to build the project.
 
-    To create a root project, select \uicontrol {File > New File or Project >
+    To create a root project, select \uicontrol File >
-    Other Project > Subdirs Project > Choose}.
+    \uicontrol {New File or Project} > \uicontrol {Other Project} >
+    \uicontrol {Subdirs Project} > \uicontrol Choose.
 
     On the \uicontrol Summary page, select \uicontrol {Finish & Add Subproject} to create
     the root project and to add another project, such as a C++ library.

doc/qtcreator/src/projects/creator-only/creator-projects-libraries.qdoc

@@ -124,7 +124,8 @@
 
         \li In the \uicontrol Projects view, right-click the project name to open the
             context menu and select
-            \uicontrol {Add Library > Internal Library > Next}.
+            \uicontrol {Add Library} > \uicontrol {Internal Library} >
+            \uicontrol Next.
 
         \li In the \uicontrol Library field, select \b mylib and click \uicontrol Next.
 

doc/qtcreator/src/projects/creator-only/creator-projects-settings-build.qdoc

@@ -164,8 +164,8 @@
 
     \section2 Adding Custom Build Steps
 
-    To add custom steps to the build settings, select \uicontrol {Add Build Step >
+    To add custom steps to the build settings, select
-    Custom Process Step}.
+    \uicontrol {Add Build Step} > \uicontrol {Custom Process Step}.
 
     By default, custom steps are enabled. To disable a custom step, select
     the \inlineimage buildstepdisable.png

doc/qtcreator/src/projects/creator-only/creator-projects-settings-code-style.qdoc

@@ -59,7 +59,7 @@
     \image qtcreator-code-style-clang-format.png "Clang Format Code Style settings in Projects mode"
 
     To specify global code style settings sets for C++ files, select
-    \uicontrol {Tools > Options > C++}.
+    \uicontrol Tools > \uicontrol Options > \uicontrol C++.
 
     To specify global code style settings sets for QML files, select \uicontrol {Tools
     > Options > Qt Quick}.

doc/qtcreator/src/projects/creator-only/creator-projects-settings-editor.qdoc

@@ -43,8 +43,8 @@
 
     You can configure the text editor according to your needs. You can specify
     editor behavior either globally for all projects or separately for each
-    project. To specify global editor behavior, select \uicontrol {Tools > Options
+    project. To specify global editor behavior, select \uicontrol Tools >
-    > Text Editor > Behavior}.
+    \uicontrol Options > \uicontrol {Text Editor} > \uicontrol Behavior.
 
     To configure the text editor behavior for the current project:
 

doc/qtcreator/src/qtcreator.qdoc

@@ -29,7 +29,6 @@
 // Run the fixnavi.pl script to adjust the links to the index order.
 // **********************************************************************
 
-
 /*!
     \contentspage{index.html}{Qt Creator}
     \page index.html
@@ -132,7 +131,7 @@
         \row
             \li {4,1} \note To report bugs and suggestions to the
                 \l{https://bugreports.qt.io/}{Qt Project Bug Tracker},
-                select \uicontrol {Help > Report Bug}.
+                select \uicontrol Help > \uicontrol {Report Bug}.
                 To copy and paste detailed information about your system to the
                 bug report, select \uicontrol Help >
                 \uicontrol {System Information}.

doc/qtcreator/src/qtquick/creator-only/creator-tutorial-create-qq-project.qdocinc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2019 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -31,8 +31,8 @@
     \list 1
 
         \li Select \uicontrol File > \uicontrol {New File or Project} >
-            \uicontrol Application > \uicontrol {Qt Quick Application - Swipe} >
+            \uicontrol {Application (Qt Quick)} >
-            \uicontrol Choose.
+            \uicontrol {Qt Quick Application - Swipe} > \uicontrol Choose.
 
         \li In the \uicontrol Name field, enter a name for the application.
 

doc/qtcreator/src/qtquick/creator-only/qtquick-app-tutorial.qdoc

@@ -1,6 +1,6 @@
 /****************************************************************************
 **
-** Copyright (C) 2019 The Qt Company Ltd.
+** Copyright (C) 2020 The Qt Company Ltd.
 ** Contact: https://www.qt.io/licensing/
 **
 ** This file is part of the Qt Creator documentation.
@@ -72,14 +72,17 @@
 
             \image qmldesigner-tutorial-design-mode.png "Transitions project in Design Mode"
 
+            \note If a view is hidden, you can show it by selecting
+            \uicontrol Window > \uicontrol Views.
+
         \li In the \uicontrol Navigator, select \uicontrol Label and press
             \key Delete to delete it.
 
-        \li Select \uicontrol Page in the navigator, and enter \e page in the
+        \li Select \uicontrol Page in \uicontrol Navigator, and enter \e page in
-            \uicontrol Id field.
+            the \uicontrol Id field in the \uicontrol Properties view.
 
         \li In \uicontrol Library > \uicontrol Assets, select qt-logo.png and
-            drag and drop it to the \e page in the navigator.
+            drag and drop it to the \e page in \uicontrol Navigator.
 
             \image qmldesigner-tutorial-user-icon.png "Image properties"
 
@@ -92,12 +95,14 @@
 
         \endlist
 
-        \li Right-click the resource file, qml.qrc, in the \uicontrol Projects
+        \li In the \uicontrol Projects view, right-click the resource file,
-            view, and select \uicontrol {Add Existing File} to add qt-logo.png
+            qml.qrc, and select \uicontrol {Add Existing File} to add
-            to the resource file for deployment.
+            qt-logo.png to the resource file for deployment.
 
-        \li Drag and drop a \uicontrol Rectangle to \e page in the navigator and
+        \li In \uicontrol Library > \uicontrol {QML Types} >
-            edit its properties.
+            \uicontrol {Qt Quick - Basic}, select \uicontrol Rectangle,
+            drag and drop it to \e page in \uicontrol Navigator, and
+            edit its properties in the \uicontrol Properties view.
 
             \image qmldesigner-tutorial-topleftrect.png "Rectangle properties"
 
@@ -131,7 +136,7 @@
         \endlist
 
         \li Drag and drop a \uicontrol {Mouse Area} type from the
-            \uicontrol Library to \e topLeftRect in the navigator.
+            \uicontrol Library to \e topLeftRect in \uicontrol Navigator.
 
         \li Click \uicontrol {Layout}, and then click the
             \inlineimage anchor-fill.png
@@ -139,9 +144,9 @@
             rectangle.
 
         \li In the \uicontrol Navigator, copy topLeftRect (by pressing
-            \key {Ctrl+C}) and paste it to the \e page in the navigator twice
+            \key {Ctrl+C}) and paste it to \e page in \uicontrol Navigator
-            (by pressing \key {Ctrl+V}). \QC renames the new instances of the
+            twice (by pressing \key {Ctrl+V}). \QC renames the new instances
-            type topLeftRect1 and topLeftRect2.
+            of the type topLeftRect1 and topLeftRect2.
 
         \li  Select topLeftRect1 and edit its properties:
 
@@ -213,16 +218,11 @@
 
     \list 1
 
-        \li Specify the window size and background color as properties of
-            the ApplicationWindow type:
-
-            \quotefromfile transitions/main.qml
-            \skipto ApplicationWindow
-            \printuntil title
-
         \li Specify an id for the Page1 type to be able to use the properties
             that you exported in \e Page1Form.ui.qml:
 
+            \quotefromfile transitions/main.qml
+            \skipto ApplicationWindow
             \printuntil page
 
         \li Add a pointer to the clicked expressions in \uicontrol mouseArea: