class QQuickWidget#

The QQuickWidget class provides a widget for displaying a Qt Quick user interface. More

Inheritance diagram of PySide6.QtQuickWidgets.QQuickWidget

Inherited by: QAbstract3DGraph, Q3DSurface, Q3DScatter, Q3DBars







This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/

Detailed Description#

This is a convenience wrapper for QQuickWindow which will automatically load and display a QML scene when given the URL of the main source file. Alternatively, you can instantiate your own objects using QQmlComponent and place them in a manually set up QQuickWidget .

Typical usage:

QQuickWidget *view = new QQuickWidget;

To receive errors related to loading and executing QML with QQuickWidget , you can connect to the statusChanged() signal and monitor for Error . The errors are available via errors() .

QQuickWidget also manages sizing of the view and root object. By default, the resizeMode is SizeViewToRootObject , which will load the component and resize it to the size of the view. Alternatively the resizeMode may be set to SizeRootObjectToView which will resize the view to the size of the root object.

Performance Considerations#

QQuickWidget is an alternative to using QQuickView and QWidget::createWindowContainer(). The restrictions on stacking order do not apply, making QQuickWidget the more flexible alternative, behaving more like an ordinary widget.

However, the above mentioned advantages come at the expense of performance:

  • Unlike QQuickWindow and QQuickView , QQuickWidget involves at least one additional render pass targeting an offscreen color buffer, typically a 2D texture, followed by drawing a texture quad. This means increased load especially for the fragment processing of the GPU.

  • Using QQuickWidget disables the threaded render loop on all platforms. This means that some of the benefits of threaded rendering, for example Animator classes and vsync driven animations, will not be available.


Avoid calling winId() on a QQuickWidget . This function triggers the creation of a native window, resulting in reduced performance and possibly rendering glitches. The entire purpose of QQuickWidget is to render Quick scenes without a separate native window, hence making it a native widget should always be avoided.

Graphics API Support#

QQuickWidget is functional with all the 3D graphics APIs supported by Qt Quick, as well as the software backend. Other backends, for example OpenVG, are not compatible however and attempting to construct a QQuickWidget will lead to problems.

Overriding the platform’s default graphics API is done the same way as with QQuickWindow and QQuickView : either by calling setGraphicsApi() early on before constructing the first QQuickWidget , or by setting the QSG_RHI_BACKEND environment variable.


One top-level window can only use one single graphics API for rendering. For example, attempting to place a QQuickWidget using Vulkan and a QOpenGLWidget in the widget hierarchy of the same top-level window, problems will occur and one of the widgets will not be rendering as expected.

Scene Graph and Context Persistency#

QQuickWidget honors isPersistentSceneGraph() , meaning that applications can decide - by calling setPersistentSceneGraph() on the window returned from the quickWindow() function - to let scenegraph nodes and other Qt Quick scene related resources be released whenever the widget becomes hidden. By default persistency is enabled, just like with QQuickWindow .

When running with the OpenGL, QQuickWindow offers the possibility to disable persistent OpenGL contexts as well. This setting is currently ignored by QQuickWidget and the context is always persistent. The OpenGL context is thus not destroyed when hiding the widget. The context is destroyed only when the widget is destroyed or when the widget gets reparented into another top-level widget’s child hierarchy. However, some applications, in particular those that have their own graphics resources due to performing custom OpenGL rendering in the Qt Quick scene, may wish to disable the latter since they may not be prepared to handle the loss of the context when moving a QQuickWidget into another window. Such applications can set the QCoreApplication::AA_ShareOpenGLContexts attribute. For a discussion on the details of resource initialization and cleanup, refer to the QOpenGLWidget documentation.


QQuickWidget offers less fine-grained control over its internal OpenGL context than QOpenGLWidget, and there are subtle differences, most notably that disabling the persistent scene graph will lead to destroying the context on a window change regardless of the presence of QCoreApplication::AA_ShareOpenGLContexts.


Putting other widgets underneath and making the QQuickWidget transparent will not lead to the expected results: the widgets underneath will not be visible. This is because in practice the QQuickWidget is drawn before all other regular, non-OpenGL widgets, and so see-through types of solutions are not feasible. Other type of layouts, like having widgets on top of the QQuickWidget , will function as expected.

When absolutely necessary, this limitation can be overcome by setting the Qt::WA_AlwaysStackOnTop attribute on the QQuickWidget . Be aware, however that this breaks stacking order. For example it will not be possible to have other widgets on top of the QQuickWidget , so it should only be used in situations where a semi-transparent QQuickWidget with other widgets visible underneath is required.

This limitation only applies when there are other widgets underneath the QQuickWidget inside the same window. Making the window semi-transparent, with other applications and the desktop visible in the background, is done in the traditional way: Set Qt::WA_TranslucentBackground on the top-level window, request an alpha channel, and change the Qt Quick Scenegraph’s clear color to Qt::transparent via setClearColor() .

Tab Key Handling#

On press of the [TAB] key, the item inside the QQuickWidget gets focus. If this item can handle [TAB] key press, focus will change accordingly within the item, otherwise the next widget in the focus chain gets focus.

class ResizeMode#

This enum specifies how to resize the view.




The view resizes with the root item in the QML.


The view will automatically resize the root item to the size of the view.

class Status#

Specifies the loading status of the QQuickWidget .




This QQuickWidget has no source set.


This QQuickWidget has loaded and created the QML component.


This QQuickWidget is loading network data.


One or more errors occurred. Call errors() to retrieve a list of errors.


Properties can be used directly when from __feature__ import true_property is used or via accessor functions otherwise.

property resizeModeᅟ: QQuickWidget.ResizeMode#

This property Determines whether the view should resize the window contents..

If this property is set to SizeViewToRootObject (the default), the view resizes to the size of the root item in the QML.

If this property is set to SizeRootObjectToView , the view will automatically resize the root item to the size of the view.

Regardless of this property, the sizeHint of the view is the initial size of the root item. Note though that since QML may load dynamically, that size may change.

See also


Access functions:
property sourceᅟ: QUrl#

This property holds The URL of the source of the QML component..

Ensure that the URL provided is full and correct, in particular, use QUrl::fromLocalFile() when loading a file from the local filesystem.


Setting a source URL will result in the QML component being instantiated, even if the URL is unchanged from the current value.

Access functions:
property statusᅟ: QQuickWidget.Status#

The component’s current status .

Access functions:


Constructs a QQuickWidget with the given parent. The default value of parent is 0.

__init__(source[, parent=None])

Constructs a QQuickWidget with the given QML source and parent. The default value of parent is 0.

__init__(engine, parent)

Constructs a QQuickWidget with the given QML engine and parent.

Note: In this case, the QQuickWidget does not own the given engine object; it is the caller’s responsibility to destroy the engine. If the engine is deleted before the view, status() will return Error .

Return type:


Returns a pointer to the QQmlEngine used for instantiating QML Components.

Return type:

.list of QQmlError

Return the list of errors that occurred during the last compile or create operation. When the status is not Error , an empty list is returned.

See also


Return type:


Returns the actual surface format.

If the widget has not yet been shown, the requested format is returned.

See also


Return type:


Renders a frame and reads it back into an image.


This is a potentially expensive operation.

Return type:


Returns the initial size of the root object.

If resizeMode is SizeRootObjectToView , the root object will be resized to the size of the view. This function returns the size of the root object before it was resized.

Return type:


Returns the offscreen QQuickWindow which is used by this widget to drive the Qt Quick rendering. This is useful if you want to use QQuickWindow APIs that are not currently exposed by QQuickWidget , for instance connecting to the beforeRendering() signal in order to draw native OpenGL content below Qt Quick’s own rendering.


Use the return value of this function with caution. In particular, do not ever attempt to show the QQuickWindow , and be very careful when using other QWindow-only APIs.


The offscreen window may be deleted (and recreated) during the life time of the QQuickWidget , particularly when the widget is moved to another QQuickWindow . If you need to know when the window has been replaced, connect to its destroyed() signal.

Return type:


See also


Getter of property resizeModeᅟ .

Return type:


This function returns the root of the context hierarchy. Each QML component is instantiated in a QQmlContext. QQmlContext’s are essential for passing data to QML components. In QML, contexts are arranged hierarchically and this hierarchy is managed by the QQmlEngine.

Return type:


Returns the view’s root item . Can be null when setSource() has not been called, if it was called with broken QtQuick code or while the QtQuick contents are being created.

sceneGraphError(error, message)#

This signal is emitted when an error occurred during scene graph initialization.

Applications should connect to this signal if they wish to handle errors, like OpenGL context creation failures, in a custom way. When no slot is connected to the signal, the behavior will be different: Quick will print the message, or show a message box, and terminate the application.

This signal will be emitted from the GUI thread.



Sets the clear color. By default this is an opaque color.

To get a semi-transparent QQuickWidget , call this function with color set to Qt::transparent, set the Qt::WA_TranslucentBackground widget attribute on the top-level window, and request an alpha channel via setFormat() .

See also


setContent(url, component, item)#


Sets the surface format for the context and offscreen surface used by this widget.

Call this function when there is a need to request a context for a given OpenGL version or profile. The sizes for depth, stencil and alpha buffers are taken care of automatically and there is no need to request those explicitly.

See also




See also


Setter of property resizeModeᅟ .



Sets the source to the url, loads the QML component and instantiates it.

Ensure that the URL provided is full and correct, in particular, use QUrl::fromLocalFile() when loading a file from the local filesystem.

Calling this method multiple times with the same URL will result in the QML component being reinstantiated.

See also


Setter of property sourceᅟ .

Return type:


Returns the source URL, if set.

See also


Getter of property sourceᅟ .

Return type:


Getter of property statusᅟ .



This signal is emitted when the component’s current status changes.

Notification signal of property statusᅟ .