- QVariant::Type deprecated, use QMetaType related APIs
- QNodeId not used as reference in for loops (nop but really noisy)
- some unused code
Pick-to: 6.0
Change-Id: I08f72181ae6eeb369ca41015a21813cd7bf05231
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Many of the examples were missing find_package() calls.
Some were missing some example install dir things.
Some missing special cases.
Some incorrectly specified library names due to missing mappings in
pro2cmake.
Some incorrectly specified target names.
Change-Id: I131a02dc679502ea6c1cdeb32962e77f09e672af
Reviewed-by: Mike Krus <mike.krus@kdab.com>
Re-generate examples, but only the chunks that handle
INSTALL_EXAMPLESDIR, because there have been so many manual changes that
were not special-cased.
Fixes: QTBUG-87331
Change-Id: I0926c015ce2733b462adba18e3dbf47621a7e679
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Christophe Giboudeaux <christophe@krop.fr>
Rename Android package name org.qtproject.qt5.android to
org.qtproject.qt.android to avoid inconsistency with Qt 6 name.
Task-number: QTBUG-86969
Change-Id: Ife5db0d7272473872231a9f3cf94171dea95945a
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
By default, Scene3D will select the RHI backend.
If QQuickWindow::graphicsApi() is set to QSGRendererInterface::OpenGLRhi
(QSG_RHI_BACKEND set to "opengl") then Qt3D will select the OpenGL
backend.
It's possible to use the OpenGL backend to RHI by setting
QQuickWindow::graphicsApi() to QSGRendererInterface::OpenGLRhi
AND setting QT3D_RENDERER to "rhi".
(Note that setting to QSGRendererInterface::OpenGL has not effect).
Change-Id: I71488ddb290ce2e30c724ddcc10c57ed8afe267b
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Its DeviceType also becomes an enum class, so needs one more layer of
namespace prefix.
Change-Id: Iec519721f30811d91348de92a11ffc82ba86e81d
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Example was referencing assets that were removed a long time ago
Change-Id: I9ab76c53d565d4579b9f7ffc9c69789d836d0159
Pick-to: 5.15
Reviewed-by: Mike Krus <mike.krus@kdab.com>
- QOpenGLEXtensions now private API in GUI
- Removed support for tessellation in GL 3
- Use QMouseEvent position
- Removed use of QDesktopWidget
- Adapt to change in QQuickWindow API
Change-Id: I79df8780b9d02c6d2a3620529f5f41daec7120fe
Reviewed-by: Mike Krus <mike.krus@kdab.com>
Trying to please CMake CI which crashes on large resources.
Will add back later.
Change-Id: I5b57e9b1326e37624bf209813c4ae7c9a0c6762f
Reviewed-by: Albert Astals Cid <albert.astals.cid@kdab.com>
- updated dependencies, excluding qtgamepad for now
- fixed issues with Q_PROPERTY not supporting forward declarations
- fixed for changes in QtQuick private API
- fixed for changes in QtOpenGLVersionFunctions API
- fixed for removal of QT_OPENGL_ES* macros
- fixed for changes in QtConcurrent API
- fixed RHI based build
Change-Id: I42ccd2f101b7f0a78e2860c6d551722bf6710a11
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
When an entity has a bounding QBoundingVolume component AND that has
a QGeometryView, the bounding volume can be computed by the core
aspect and the results get pulled to the render backend.
Otherwise, we use the old code which computes the bounding volume
in the render aspect.
This means we have 2 jobs to compute bounding volumes and that the core
version must complete before the render aspect runs.
Change-Id: I4de45e48fa0c4d40d3d5084f387abfed5ea1a2f8
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
In Extras, make QTorusMesh and others a QGeometryView rather than
a QGeometryRenderer. Requires changes to scene graphs here and there
but going forward there simple shapes could be used as proxies for
picking or collision detection, etc.
Change-Id: Id488e064080dfd303e448aba11e6b242236b81d4
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
These examples show very tiny UI elements on Android devices,
thus enabling HighDPI.
Task-number: QTBUG-80717
Change-Id: Ibc1a82679e36d74ab6f6d51a4a5b06925f913b84
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Many are moving to opengl module in qt6, will make merging
easier.
Change-Id: I0ad08510e6999a5d887d9197fe2cb0dc21919fb9
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Can be activated at adding a QDebugOverlay in the frame graph to
identify which surface it should be renderer one (renders only
once on first branch that contains such a node).
Can be also activated on the forward renderer from Qt3DExtras.
- Shows information about FPS and number of
jobs/renderviews/commands/vertices/entities/geometries/textures...
- Allows to toggle job and gl call tracing and open folder where
trace files are stored
- Windows to show and dump glinfo and renderview/command details to the
console
Change-Id: I286ff85760e8f8f0604a23458883ff22229bda94
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
- Add (basic) documentation for Qt3DAnimation::QAnimationCallback.
- Add missing namespace qualifiers for \class, \fn, \instantiates,
\sa, and \property commands.
- Remove linking to example file pages, as QDoc no longe treats them
as linkable targets.
- Fix function/QML method parameter documentation
- Fix missing \qmlproperty types
- Fix linking to QKeyEvent in QtGui.
- Move Qt3DRender::Quick namespace documentation to where QDoc can
see it.
- Add enum documentation for
Qt3DRender::QBlitFramebuffer::InterpolationMethod and
Qt3DRender::QMesh::Status.
- Other minor fixes
This brings the current warning count to zero.
Fixes: QTBUG-79822
Change-Id: I1154a7f9c34917a3f240e99da0e7a300be7d65a0
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
The bundled_in_lib and bundled_in_assets entries have been removed,
so all manifests have to be updated to no longer refer to these.
In addition, android-16 is no longer supported, so the minimum SDK
versions have to be updated.
Change-Id: Id01326df5522195647eb107b60ea7e637a950bb3
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Essentially use 10^3 KM instead of KM so that we don't end up
with too much precision in the positions which can then result
in the camera flickering when the viewMatrix is computed for
rendering
Change-Id: Id2f878c2e1ccd22a2e72a3494d2e7f623f2b4eb6
Reviewed-by: Mike Krus <mike.krus@kdab.com>
Allows to render several 3D scenes using a single Scene3D. To be used when
you need multiple Scene3D instances.
[ChangeLog] Introduce Scene3DView to render multiple distinct 3D scenes
Change-Id: I5d51c5935218cc84c15d57def3703aa0d92040ba
Reviewed-by: Mike Krus <mike.krus@kdab.com>
The default compositing mode is FBO.
One of the problematic aspects of Scene3D is its round trip
through a FBO, which is moderately expensive on low-end hardware,
although it makes it a fully fledged Qt Quick 2 item. If one
wants MSAA then things are even worse, as an intermediate MS'ed
FBO is needed, then resolving into the final one, whose color
texture is then sampled.
However, there's a significant use case for which these FBOs
can be avoided, and that's the case of a 3D scene "below" other
QQ2 content. In this setup, Qt3D can simply render to the
screen, driven by QQ2; then QQ2 can draw on top.
(It's the typical "underlay" scenario.) This can be enabled by setting
the compositing mode to Underlay
[ChangeLog] Scene3D add compositingMode property. Allows underlay rendering.
Task-number: QTBUG-74977
Change-Id: I1ec5f5d60eab45835dbdb2596a7bf1b2ac3624e0
Reviewed-by: Mike Krus <mike.krus@kdab.com>
The only noteworth change is where a loop around spy.events modified
the container using takeFirst(). There was no reason to do so, so it
was changed to use the loop variable instead of the result of taking.
Change-Id: I02c62a7c2efc5d042c6e669fe5daddd7da7e85d2
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
Mike Krus
Alexandru Croitor
Paul Lemire
Joerg Bornemann
Assam Boudjelthia
Jean-Michaël Celerier
Edward Welbourne
Qt Submodule Update Bot
Jean-Michaël Celerier
Antti Määttä
Mauro Persano
Topi Reinio
Eskil Abrahamsen Blomfeldt
Liang Qi
Marc Mutz