Using a table with code snippets in different columns will cause the
table to expand outside of the page width, forcing the user to scroll
horizontally. In addition, in mobile view, the table with code snippets
messes up the entire width of the page.

Fixes: QTBUG-104156
Change-Id: I36341a5da162cd88961ee1f8741b166b167f8770
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
(cherry picked from commit b6d3f84c2a2bd7bed7a85618a30e05925bc2b6c0)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

A previous patch 5647527a8cde84b51fff66fc482f02435770b3dd causes
a regression. The purpose of the patch, that caused this regression,
was to update the pressPos variables, in cases where the contentItem's
geometry was modified externally, while a user were dragging the
contentItem around.

The mistake that was made, was how width and height changes were
handled. We had previously added logic in setContentWidth() and
setContentHeight() that would call fixup() (with immediate fixupMode)
to ensure that the contentItem would immediately be repositioned
inside the flickable's viewport, if the contentItem was being dragged.

It turns out that setContentWidth() and setContentHeight() are being
called from QQuickItemViewPrivate::updateViewport(), which happens
quite often, while dragging. This would make fixup() and dragging
constantly interfere with each other, since they'd not always agree on
a specific position for the contentItem.

This patch reverts the changes made to setContentWidth() and
setContentHeight(), since it turns out that those changes weren't
necessary after all. QQuickFlickablePrivate::itemGeometryChanged() only
calls viewportMoved() on x and y changes anyways.

Done-with: Jan Arve Sæther <jan-arve.saether@qt.io>
Done-with: Santhosh Kumar Selvaraj <santhosh.kumar.selvaraj@qt.io>
Fixes: QTBUG-109140
Change-Id: I0bddf8685d3afc1ae04b2c092212d3c1bd742c3b
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
(cherry picked from commit b307bf3c4f63c6e04874a972c747f18e18ddc199)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

QQuickWindow::QQuickWindow(QQuickRenderControl *control)
should be part of the public API. The user can use
QQuickRenderControl with QQuickWindow to control the
scenegraph rendering. This constructor is used in the
QQuickRenderControl example.

Change-Id: I1bb38d64173c24ba835137897ef915dfde83b1f3
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
(cherry picked from commit 7454d3b612eab92b8e91741fc1c51311cf80c3a2)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

The items that reject drag events (specifically onEntered in DropArea)
should not be retriggered with DragEnter event until entered once again.

Fixes: QTBUG-74496
Change-Id: I241a6004da6382685be89fe8a001b98dfde5c8a2
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 0b7374fefa1abf08e956bc5d34008352144bd9ae)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

Otherwise it's only possible to build these projects on the command
line with qt-cmake-standalone-test.

Task-number: QTBUG-93020
Change-Id: I84e5bd2b6b3bb7cb8deac22ec417af793ae8c1d6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 04926f4320bbb79816eb7b091d02dcf649befcf1)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

In case antialiasing is disabled the QFontEngine::Format_Mono is used
to render in the glyph cache.
In this format the padding needs to be 8-bit aligned.

Fixes: QTBUG-107038
Change-Id: Icc3c69fe0395cea9954c2fa07c39e7769fc91800
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
(cherry picked from commit cba96b3a97977f71931f311db9d5644d1d74d694)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

For some controls, (e.g. TextInput and Text) we can get changes in
baseline offset when they change their height. These changes will
invalidate the layout and generate a polish event.

This means that during a rearrange of a layout with TextInput children, it
might change the height of its children. This might change the baselineOffset
of these children, which again will cause the layout to have to be invalidated
(and rearranged again) This double-loop is unnecessary if the layout is not
supposed to align these items by their baselines, so we add some conditions to
see if we really need to connect to the baselineOffsetChanged() signal.

This also fixes a bug observed in the color dialog, where the
semi-recursiveness described above lead to a problem with that the alpha
TextField of the RGBA color input was *not* laid out by the parent RowLayout

Fixes: QTBUG-105899
Change-Id: If66b4bbde6a37c962b157e166c883ba20ff24c21
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 1fe641c50defed77590e2eba9d33e6c3746fa832)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

Works anyway because the data layout (a single m_node member) is the same
for all the materials, but let's correct the casts.

Fixes: QTBUG-106824
Change-Id: I84038b04ca03339bdefc61d5780b35309fcf6670
Reviewed-by: Andy Nichols <andy.nichols@qt.io>
(cherry picked from commit 2afb9fe157ff7ead678f1b29f3c2955e277e7d1c)
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>

We want to use qt_add_qml_module() instead of qt_add_resources().

Note that this change also changes the target to 'galleryexample', which
will also affect the name of the executable. I'm making that change in
order to be consistent with other examples.

Task-number: QTBUG-98130
Change-Id: I1ed1af18a01b652673828c60e803cb2ea9b04a3d
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit fa00dee21ccd6f7ec159a8d88756df6e778b8d32)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

This caught my attention while reviewing a related fix
(4933bd6351feec988746af647c391c46483f049a)

Task-number: QTBUG-106594
Change-Id: Ie8c7fb2d9e504b14a924eca72a87295d8764cf39
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
(cherry picked from commit a7c8bd27e390db9d0d401f9008ceb4130da53d6f)