Doc: Remove references to Qt 4 and < Qt 5.15

Leave only mentions to things visible in the UI and
to compatibility functions.

Fixes: QTCREATORBUG-30883
Change-Id: Id63d791f79363c2f4c2602bb8c0ed656a9ceab29
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
This commit is contained in:
Leena Miettinen
2024-05-31 13:29:51 +02:00
parent 3c71998e34
commit 440c579ec0
10 changed files with 32 additions and 126 deletions

View File

@@ -113,7 +113,7 @@
LTTng is a tracing toolkit for Linux that you can apply on embedded Linux LTTng is a tracing toolkit for Linux that you can apply on embedded Linux
systems to find out how to optimize the startup time of an application. systems to find out how to optimize the startup time of an application.
Since Qt 5.13, Qt has a set of kernel trace points and a tracing Qt has a set of kernel trace points and a tracing
subsystem for custom user space trace points. subsystem for custom user space trace points.
\section2 Configuring the Kernel \section2 Configuring the Kernel

View File

@@ -131,22 +131,24 @@
C:\Users\Username\AppData\Local\QtProject\qtcreator\android\sdk_definitions.json C:\Users\Username\AppData\Local\QtProject\qtcreator\android\sdk_definitions.json
\endcode \endcode
For example, the SDK configuration file sets the NDK version 19.2.5345600 For example, the SDK configuration file sets the NDK version 22.1.7171670
for use with Qt 5.12.0 to 5.12.5 and Qt 5.13.0 to 5.13.1: for use with Qt 6.3, Qt 6.2, and Qt 5.15.9 to 5.15.20:
\badcode \badcode
"specific_qt_versions": [ "specific_qt_versions": [
{ { "versions": ["6.3", "6.2", "5.15.[9-20]"],
"versions": ["5.12.[0-5]", "5.13.[0-1]"], "sdk_essential_packages": ["build-tools;31.0.0", "ndk;22.1.7171670"]
"sdk_essential_packages": ["build-tools;28.0.2", "ndk;19.2.5345600"], },
"ndk_path": "ndk/19.2.5345600"
}
] ]
\endcode \endcode
You can view the latest version of the configuration file that is up-to-date You can view the latest version of the configuration file that is up-to-date
with the Android SDK and NDK changes, \l{sdk_definitions.json}, in Git. with the Android SDK and NDK changes, \l{sdk_definitions.json}, in Git.
\note For Qt 6.5 or later, \QC reads the NDK version that was used for
building Qt from \c modules/Core.json and uses it instead of the version
in \c sdk_definitions.json.
\sa {Android}{How To: Develop for Android}, \sa {Android}{How To: Develop for Android},
{Developing for Android} {Developing for Android}
*/ */

View File

@@ -25,10 +25,6 @@
information about the state of the UI, and inspect QML properties and information about the state of the UI, and inspect QML properties and
JavaScript variables, as well as change their values temporarily at runtime. JavaScript variables, as well as change their values temporarily at runtime.
\if defined(qtcreator)
\note You need Qt 5.0 or later to debug Qt Quick projects.
\endif
For an example of how to debug Qt Quick Projects, see For an example of how to debug Qt Quick Projects, see
\l{Debugging a Qt Quick Application}. \l{Debugging a Qt Quick Application}.
@@ -86,7 +82,7 @@
rebuild the project. rebuild the project.
\li To debug applications on \l{glossary-device}{devices}, check that \li To debug applications on \l{glossary-device}{devices}, check that
Qt 5.0, or later, libraries are installed on the device and Qt libraries are installed on the device and
\l{Run on many platforms}{select the corresponding kit for the device} \l{Run on many platforms}{select the corresponding kit for the device}
before you start debugging. before you start debugging.
@@ -250,12 +246,6 @@
application to jump to their definitions in the code. The properties of the application to jump to their definitions in the code. The properties of the
selected item are displayed in the \uicontrol {Locals} view. selected item are displayed in the \uicontrol {Locals} view.
\if defined(qtcreator)
The \uicontrol Select tool will be enabled either if your application is
using Qt 5.7 or later, or if your application is using an earlier version
of Qt and is based on the \c QQuickView class.
\endif
You can also view the item hierarchy in the running application: You can also view the item hierarchy in the running application:
Double-click an item in the running application to cycle through the item Double-click an item in the running application to cycle through the item

View File

@@ -417,18 +417,18 @@
\image qtcreator-options-texteditor-behavior-file-encodings.png {File encoding preferences} \image qtcreator-options-texteditor-behavior-file-encodings.png {File encoding preferences}
Qt 5 and Qt 6 require UTF-8 encoded source files, and therefore the default Qt requires UTF-8 encoded source files, and therefore the default
encoding is set to \uicontrol UTF-8. encoding is set to \uicontrol UTF-8.
Detecting the correct encoding is tricky, so \QC will not try to do so.
Instead, it displays the following error message when you try to edit a file If you try to edit a file that is not UTF-8 encoded, you see the following
that is not UTF-8 encoded: \uicontrol {Error: Could not decode "filename" with error message: \uicontrol {Error: Could not decode "filename" with
"UTF-8"-encoding. Editing not possible.} "UTF-8"-encoding. Editing not possible.}
To resolve the issue, use a file conversion tool to convert the file To resolve the issue, use a file conversion tool to convert the file
encoding to UTF-8 when developing Qt 5 applications. Otherwise, conversion encoding to UTF-8. Otherwise, conversion of string constants to
of string constants to QString might not work as expected. QString might not work as expected.
If you develop only Qt 4 applications or other than Qt applications, you If you do not develop Qt applications, you
can set other encoding options as the default encoding. Select the can set other encoding options as the default encoding. Select the
\uicontrol System option to use the file encoding used by your system. \uicontrol System option to use the file encoding used by your system.

View File

@@ -849,8 +849,7 @@
\section1 Blacklisting Tests \section1 Blacklisting Tests
Since Qt 5.4, you can add a BLACKLIST file for tests. It is mainly used A BLACKLIST file for tests is mainly used internally by the Qt CI system.
internally by the Qt CI system.
\table \table
\header \header

View File

@@ -121,14 +121,10 @@
\b {The Qt API Reference Documentation is missing and context help does \b {The Qt API Reference Documentation is missing and context help does
not find topics. What can I do?} not find topics. What can I do?}
\QC comes fully integrated with Qt documentation and examples using Install a Qt version and Qt documentation with \QOI.
the Qt Help plugin. The integrated Qt Reference Documentation is available
for Qt 4.4 and later. \QC and other Qt deliverables have
documentation as .qch files. All the documentation is accessible in the
\uicontrol Help mode.
To view the documentation that is available and to add documentation, To view the installed documentation (.qch files) and to add documentation,
select \preferences > \uicontrol Help > go to \preferences > \uicontrol Help >
\uicontrol Documentation. For more information, see \uicontrol Documentation. For more information, see
\l{Add external documentation}. \l{Add external documentation}.

View File

@@ -16,8 +16,8 @@
the necessary \l{Kits}{kits} to build applications for and run them on the necessary \l{Kits}{kits} to build applications for and run them on
configured iOS devices. configured iOS devices.
You only need Qt libraries that are built for iOS. You can install them as You only need Qt libraries that are built for iOS. You can install Qt for iOS
part of Qt 5.2, or later. with \QOI.
\section1 iOS 17 Devices \section1 iOS 17 Devices

View File

@@ -45,8 +45,7 @@
\li libxft-dev \li libxft-dev
\li libxi-dev \li libxi-dev
\li libxrandr-dev \li libxrandr-dev
\li libgl-dev and libglu-dev if you use Qt OpenGL (deprecated \li libgl-dev and libglu-dev if you use Qt GUI OpenGL functions
in Qt 5) or Qt GUI OpenGL functions
\endlist \endlist
\section1 macOS \section1 macOS

View File

@@ -149,8 +149,7 @@
imports that are used in the QML files. imports that are used in the QML files.
You can add imports later to combine Qt Quick basic types with You can add imports later to combine Qt Quick basic types with
Qt Quick Controls, Qt Quick Dialogs, and Qt Quick Layouts (available Qt Quick Controls, Qt Quick Dialogs, and Qt Quick Layouts.
since Qt 5.1).
\li Select the \uicontrol {Use Qt Virtual Keyboard} check box to add \li Select the \uicontrol {Use Qt Virtual Keyboard} check box to add
support for \l{Qt Virtual Keyboard} to the application. support for \l{Qt Virtual Keyboard} to the application.

View File

@@ -261,33 +261,24 @@
of the code the event is associated with. of the code the event is associated with.
The following types of events are displayed in the timeline view on one or The following types of events are displayed in the timeline view on one or
several rows. The availability of event types depends on the Qt version that several rows.
you build the application with and the Qt Quick version you use.
\table \table
\header \header
\li Event Category \li Event Category
\li Description \li Description
\li Minimum Qt Version
\li Qt Quick Version
\row \row
\li \uicontrol {Pixmap Cache} \li \uicontrol {Pixmap Cache}
\li Displays the general amount of pixmap data cached, in pixels. In \li Displays the general amount of pixmap data cached, in pixels. In
addition, displays a separate event for each picture being loaded, addition, displays a separate event for each picture being loaded,
with specifics about its file name and size. with specifics about its file name and size.
\li Qt 5.1
\li Qt Quick 2
\row \row
\li \uicontrol {Scene Graph} \li \uicontrol {Scene Graph}
\li Displays the time when scene graph frames are rendered and some \li Displays the time when scene graph frames are rendered and some
additional timing information for the various stages executed to do additional timing information for the various stages executed to do
so. so.
\li Qt 5.1
\li Qt Quick 2
\row \row
\li \uicontrol {Memory Usage} \li \uicontrol {Memory Usage}
\li Displays block allocations of the JavaScript memory manager. \li Displays block allocations of the JavaScript memory manager.
@@ -300,82 +291,49 @@
The second row displays the actual usage of the allocated memory. The second row displays the actual usage of the allocated memory.
This is the amount of JavaScript heap the application has actually This is the amount of JavaScript heap the application has actually
requested. requested.
\li Qt 5.4
\li Qt Quick 2
\row \row
\li \uicontrol {Input Events} \li \uicontrol {Input Events}
\li Displays mouse and keyboard events. \li Displays mouse and keyboard events.
\li Qt 4.7.4
\li Qt Quick 1 or Qt Quick 2
\row \row
\li \uicontrol Painting \li \uicontrol Painting
\li Displays the time spent painting the scene for each frame. \li Not used.
\li Qt 4.7.4
\li Qt Quick 1
\row \row
\li \uicontrol Animations \li \uicontrol Animations
\li Displays the amount of animations that are active and the frame \li Displays the amount of animations that are active and the frame
rate that they are running at. rate that they are running at.
Information about render thread animations is displayed for Render thread animations are shown on a separate row.
applications that are built with Qt 5.3 or later. Render thread
animations are shown in a separate row then.
\li Qt 5.0 (Qt 5.3)
\li Qt Quick 2
\row \row
\li \uicontrol Compiling \li \uicontrol Compiling
\li Displays the time spent compiling the QML files. \li Displays the time spent compiling the QML files.
\li Qt 4.7.4
\li Qt Quick 1 or Qt Quick 2
\row \row
\li \uicontrol Creating \li \uicontrol Creating
\li Displays the time spent creating the elements in the scene. In Qt \li Displays the time spent creating the elements in the scene.
Quick 2, creation of elements takes place in two stages. The first The creation of elements takes place in two stages. The first
stage is for the creation of the data structures, including child stage is for the creation of the data structures, including child
elements. The second stage represents the completion callbacks. Not elements. The second stage represents the completion callbacks. Not
all elements trigger completion callbacks, though. The stages are all elements trigger completion callbacks, though. The stages are
shown as separate events in the timeline. shown as separate events in the timeline.
For Qt Quick 2 applications compiled with versions of Qt before
5.2.1 only the creation of top-level elements is shown, as single
events.
\li Qt 4.7.4 (Qt 5.2.1)
\li Qt Quick 1 or Qt Quick 2
\row \row
\li \uicontrol Binding \li \uicontrol Binding
\li Displays the time when a binding is evaluated and how long the \li Displays the time when a binding is evaluated and how long the
evaluation takes. evaluation takes.
\li Qt 4.7.4
\li Qt Quick 1 or Qt Quick 2
\row \row
\li \uicontrol {Handling Signal} \li \uicontrol {Handling Signal}
\li Displays the time when a signal is handled and how long the \li Displays the time when a signal is handled and how long the
handling takes. handling takes.
\li Qt 4.7.4
\li Qt Quick 1 or Qt Quick 2
\row \row
\li \uicontrol JavaScript \li \uicontrol JavaScript
\li Displays the time spent executing the actual JavaScript behind \li Displays the time spent executing the actual JavaScript behind
bindings and signal handlers. It lists all the JavaScript functions bindings and signal handlers. It lists all the JavaScript functions
you may be using to evaluate bindings or handle signals. you may be using to evaluate bindings or handle signals.
\li Qt 5.3
\li Qt Quick 2
\row \row
\li \uicontrol Quick3D \li \uicontrol Quick3D
\li Displays the time spent rendering Qt Quick 3D frames, timing information \li Displays the time spent rendering Qt Quick 3D frames, timing information
for frame preparation and synchronization, particle system update times for frame preparation and synchronization, particle system update times
and particle update count, as well as texture and mesh memory allocations and particle update count, as well as texture and mesh memory allocations
and memory consumption. and memory consumption.
\li Qt 6.3
\li Qt Quick 3D
This event type is available since Qt 6.3.
\endtable \endtable
\section2 Analyzing Scene Graph Events \section2 Analyzing Scene Graph Events
@@ -399,7 +357,6 @@
\li Render Loop Types \li Render Loop Types
\li Label in output of QSG_RENDER_TIMING \li Label in output of QSG_RENDER_TIMING
\li Description \li Description
\li Caveats
\row \row
\li \uicontrol {Polish} \li \uicontrol {Polish}
\li GUI \li GUI
@@ -407,8 +364,6 @@
\li polish \li polish
\li Final touch-up of items before they are rendered using \li Final touch-up of items before they are rendered using
QQuickItem::updatePolish(). QQuickItem::updatePolish().
\li Versions of Qt prior to Qt 5.4 record no polish times for the basic
render loop and incorrect ones for the windows render loop.
\row \row
\li \uicontrol {GUI Thread Wait} \li \uicontrol {GUI Thread Wait}
\li GUI \li GUI
@@ -419,14 +374,12 @@
the same mutex at \uicontrol {GUI Thread Sync}. If this starts long the same mutex at \uicontrol {GUI Thread Sync}. If this starts long
before \uicontrol {Render Thread Sync}, there is \e free time in the GUI before \uicontrol {Render Thread Sync}, there is \e free time in the GUI
thread you could be using for running additional QML or JavaScript. thread you could be using for running additional QML or JavaScript.
\li None
\row \row
\li \uicontrol {GUI Thread Sync} \li \uicontrol {GUI Thread Sync}
\li GUI \li GUI
\li Threaded \li Threaded
\li blockedForSync \li blockedForSync
\li The time the GUI thread is blocked, waiting for the render thread. \li The time the GUI thread is blocked, waiting for the render thread.
\li None
\row \row
\li \uicontrol {Animations} \li \uicontrol {Animations}
\li GUI \li GUI
@@ -437,7 +390,6 @@
animation events will be shown when using the basic render loop. animation events will be shown when using the basic render loop.
Watch the \uicontrol {Animations} category to see animation timing in Watch the \uicontrol {Animations} category to see animation timing in
this case. this case.
\li None
\row \row
\li \uicontrol {Render Thread Sync} \li \uicontrol {Render Thread Sync}
\li Render \li Render
@@ -445,7 +397,6 @@
\li Frame rendered ... sync \li Frame rendered ... sync
\li Synchronizing the QML state into the scene graph using \li Synchronizing the QML state into the scene graph using
QQuickItem::updatePaintNode(). QQuickItem::updatePaintNode().
\li None
\row \row
\li \uicontrol {Render} \li \uicontrol {Render}
\li Render \li Render
@@ -455,20 +406,12 @@
uploading all the necessary data to the GPU. This is the \e gross uploading all the necessary data to the GPU. This is the \e gross
render time. Do not confuse it with the \e net \uicontrol{Render Render} render time. Do not confuse it with the \e net \uicontrol{Render Render}
time below. time below.
\li With versions of Qt prior to Qt 5.5, the gross render time and the
below breakup of render times may be misaligned by some
microseconds due to different, unsynchronized timers being used to
measure them. For example \uicontrol {Render Preprocess} might seem to
start before \uicontrol {Render Thread Sync} is finished.
\row \row
\li \uicontrol {Swap} \li \uicontrol {Swap}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li Frame rendered ... swap \li Frame rendered ... swap
\li Swapping frames after rendering. \li Swapping frames after rendering.
\li The output of swap times triggered by setting QSG_RENDER_TIMING is
incorrect for the basic render loop and versions of Qt prior to
Qt 5.4. QML Profiler shows the correct swap times.
\row \row
\li \uicontrol {Render Preprocess} \li \uicontrol {Render Preprocess}
\li Render \li Render
@@ -476,8 +419,6 @@
\li time in renderer ... preprocess \li time in renderer ... preprocess
\li Calling QSGNode::preprocess() on all nodes that need to be \li Calling QSGNode::preprocess() on all nodes that need to be
preprocessed. This is part of the gross \uicontrol {Render} step. preprocessed. This is part of the gross \uicontrol {Render} step.
\li May not be properly aligned with \uicontrol {Render} with versions of Qt
prior to Qt 5.5.
\row \row
\li \uicontrol {Render Update} \li \uicontrol {Render Update}
\li Render \li Render
@@ -489,8 +430,6 @@
with state from the GUI thread. In \uicontrol {Render Update}, all the with state from the GUI thread. In \uicontrol {Render Update}, all the
nodes are combined to create the final scene. This is part of the nodes are combined to create the final scene. This is part of the
gross \uicontrol {Render} step. gross \uicontrol {Render} step.
\li May not be properly aligned with \uicontrol {Render} with versions of Qt
prior to Qt 5.5.
\row \row
\li \uicontrol {Render Bind} \li \uicontrol {Render Bind}
\li Render \li Render
@@ -498,8 +437,6 @@
\li time in renderer ... binding \li time in renderer ... binding
\li Binding the correct framebuffer for OpenGL rendering. This is part \li Binding the correct framebuffer for OpenGL rendering. This is part
of the gross \uicontrol {Render} step. of the gross \uicontrol {Render} step.
\li May not be properly aligned with \uicontrol {Render} with versions of Qt
prior to Qt 5.5.
\row \row
\li \uicontrol {Render Render} \li \uicontrol {Render Render}
\li Render \li Render
@@ -507,38 +444,30 @@
\li time in renderer ... rendering \li time in renderer ... rendering
\li The actual process of sending all the data to the GPU via OpenGL. \li The actual process of sending all the data to the GPU via OpenGL.
This is part of the gross \uicontrol {Render} step. This is part of the gross \uicontrol {Render} step.
\li May not be properly aligned with \uicontrol {Render} with versions of Qt
prior to Qt 5.5.
\row \row
\li \uicontrol {Material Compile} \li \uicontrol {Material Compile}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li shader compiled \li shader compiled
\li Compiling GLSL shader programs. \li Compiling GLSL shader programs.
\li None
\row \row
\li \uicontrol {Glyph Render} \li \uicontrol {Glyph Render}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li glyphs ... rendering \li glyphs ... rendering
\li Rendering of font glyphs into textures. \li Rendering of font glyphs into textures.
\li Versions of Qt prior to Qt 5.4 report incorrect times for these
events.
\row \row
\li \uicontrol {Glyph Upload} \li \uicontrol {Glyph Upload}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li glyphs ... upload \li glyphs ... upload
\li Uploading of glyph textures to the GPU. \li Uploading of glyph textures to the GPU.
\li Versions of Qt prior to Qt 5.4 report incorrect times for these
events.
\row \row
\li \uicontrol {Texture Bind} \li \uicontrol {Texture Bind}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li plain texture ... bind \li plain texture ... bind
\li Binding a texture in the OpenGL context using glBindTextures. \li Binding a texture in the OpenGL context using glBindTextures.
\li None
\row \row
\li \uicontrol {Texture Convert} \li \uicontrol {Texture Convert}
\li Render \li Render
@@ -546,35 +475,30 @@
\li plain texture ... convert \li plain texture ... convert
\li Converting the format and downscaling an image to make it suitable \li Converting the format and downscaling an image to make it suitable
for usage as a texture. for usage as a texture.
\li None
\row \row
\li \uicontrol {Texture Swizzle} \li \uicontrol {Texture Swizzle}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li plain texture ... swizzle \li plain texture ... swizzle
\li Swizzling the texture data on the CPU if necessary. \li Swizzling the texture data on the CPU if necessary.
\li None
\row \row
\li \uicontrol {Texture Upload} \li \uicontrol {Texture Upload}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li plain texture ... upload / atlastexture uploaded \li plain texture ... upload / atlastexture uploaded
\li Uploading the texture data to the GPU. \li Uploading the texture data to the GPU.
\li None
\row \row
\li \uicontrol {Texture Mipmap} \li \uicontrol {Texture Mipmap}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li plain texture ... mipmap \li plain texture ... mipmap
\li Mipmapping a texture on the GPU. \li Mipmapping a texture on the GPU.
\li None
\row \row
\li \uicontrol {Texture Delete} \li \uicontrol {Texture Delete}
\li Render \li Render
\li Threaded, Basic, Windows \li Threaded, Basic, Windows
\li plain texture deleted \li plain texture deleted
\li Deleting a texture from the GPU that became unnecessary. \li Deleting a texture from the GPU that became unnecessary.
\li None
\endtable \endtable
\section2 Analyzing Qt Quick 3D Events \section2 Analyzing Qt Quick 3D Events
@@ -676,9 +600,6 @@
To copy the contents of one view or row to the clipboard, select To copy the contents of one view or row to the clipboard, select
\uicontrol {Copy Table} or \uicontrol {Copy Row} in the context menu. \uicontrol {Copy Table} or \uicontrol {Copy Row} in the context menu.
JavaScript events are shown in the \uicontrol Statistics view only for applications
that use Qt Quick 2 and are built with Qt 5.3 or later.
\section2 Visualizing Statistics as Flame Graphs \section2 Visualizing Statistics as Flame Graphs
The \uicontrol {Flame Graph} view shows a more concise statistical overview The \uicontrol {Flame Graph} view shows a more concise statistical overview