QWindowContainer: Improve docs to mention new change in behavior

Specify that since 6.8 tab focus can transfer in and out of the
embedded window if using a Qt Quick based window.

Pick-to: 6.8
Change-Id: I21d04457ee79497431f889e261f1cb6bd9fd39ee
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
(cherry picked from commit 059210b17e50fd7c45af4ca0631ddcf8dd7c67f8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Doris Verria 2025-01-27 14:46:12 +01:00 committed by Qt Cherry-pick Bot
parent bcc0e6124a
commit 83226ed3d0

View File

@ -156,11 +156,13 @@ public:
instance have any focus policy and it will delegate focus to the
window via a call to QWindow::requestActivate(). However,
returning to the normal focus chain from the QWindow instance will
be up to the QWindow instance implementation itself. For instance,
when entering a Qt Quick based window with tab focus, it is quite
likely that further tab presses will only cycle inside the QML
application. Also, whether QWindow::requestActivate() actually
gives the window focus, is platform dependent.
be up to the QWindow instance implementation itself. Also, whether
QWindow::requestActivate() actually gives the window focus, is
platform dependent.
Since 6.8, if embedding a Qt Quick based window, tab presses will
transition in and out of the embedded QML window, allowing focus to move
to the next or previous focusable object in the window container chain.
\li Using many window container instances in a QWidget-based
application can greatly hurt the overall performance of the