| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
Qt 6.2.13-lts release
Conflicts solved:
dependencies.yaml
Change-Id: I3cbe1ce4293179888e236dd1a3a299cd2c66c950
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
DragHandler docs have been showing TapHandler code snippets, because
both DragHandler and TapHandler inherit properties from
PointerDeviceHandler, which is abstract and uses TapHandler code
snippets in some of its property documentation.
Override documentation for acceptedDevices, acceptedModifiers,
acceptedPointerTypes and margin by adding to the DragHandler class, and
add testable snippets for a couple of them. draggableGridView is adapted
from examples/quick/draganddrop/views/gridview.qml.
Fixes: QTBUG-119866
Change-Id: I9f98d831ec1691c84da6a38a7625f9aba086cebf
Reviewed-by: Santhosh Kumar <santhosh.kumar.selvaraj@qt.io>
(cherry picked from commit 7ddbb8f972fadc9073d1a8fd651dc08783b92a3a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 8890effa5f9bd702ff9abd781947ff3eb5a3510f)
(cherry picked from commit 05106ec5794f453d1d5fd7e9b24507c59f3c7bdc)
(cherry picked from commit 39c3655d2d770e6d1daf252efcf5a89e2a98bbac)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt 6.2.12-lts release
Conflicts solved:
dependencies.yaml
Change-Id: Ia7410afbc9d94f061fb13da84b6361428725b530
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
grabToImage() is asynchronous. 4b982c744f538a24e21a2af146c45f93d27dd1cb
started it on mouse press, which generally gave it enough time before
the QDrag became active; but 5971a6faaa1124f5ef3f0b42d4ed0298cf8096a3
changed it to call grabToImage() in DragHandler.onActiveChanged, which
means waiting until the drag threshold is exceeded. (DragHandler doesn't
offer a way to detect when the point is pressed. One could probably use
a separate TapHandler or PointHandler just to detect the press; but
that's also inefficient and inconvenient.) If we also bind Drag.active
to DragHandler.active, it's very likely that the binding is updated
before grabToImage() is done; and as documented, setting imageSource
after the drag has started has no effect (that in turn is a limitation
in QDrag and the platform support, probably a limitation on actual
platforms). So just wait until the screen-grab is done before setting
Drag.active, as a workaround for now.
This is a step back in declarativeness, using JS rather than a binding.
But setting imageSource to a screen-grab unfortunately requires JS
anyway; so we might as well delay making the Drag active until the
screen-grab is done.
Fixes: QTBUG-112673
Fixes: QTBUG-115491
Change-Id: I0317613aa0288ad99b55ebd8a470500432b2ea02
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
(cherry picked from commit a3dea1b4f8e20babb84c501e578a9208961b7ca7)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 85f6ffc9b8d511b7bf01daacd179df88b9a54dee)
(cherry picked from commit 9d1e8deefcbba6cfb343406dd2536226525535f6)
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt 6.2.11-lts release
Conflicts solved:
dependencies.yaml
Change-Id: I088fe99748b323fbdf49c3766c262eb2a05131d9
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pick-to: 5.15
Change-Id: Idb7e0f0dea262592ca39e8d42298bb51c91281cd
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Reviewed-by: Mike Trahearn <mtrahearn@topcon.com>
(cherry picked from commit 033fd3aa8c7c881697d4eb8d7e143d3088ca117f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 21bc5e786e25b59f3c09a67359958453c2b3be60)
(cherry picked from commit 0fa32a7dea2a5cf0bdf562818ab2fec7e1bcc35d)
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt 6.2.10-lts release
Conflicts solved:
dependencies.yaml
Change-Id: Ibdf006fa08cddc80ad30fb9ce1089305729d4ece
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Change the code that is quoted so that the indenting looks sane
- Make it possible to copy and run the first snippet without
modification
- Make it easier to copy and run the second snippet without
modification
- Move itemGrab.qml to item sub-directory
- Generally tidy up
Change-Id: I608b7a6025b9866c14b84420ae64827965a7519f
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
(cherry picked from commit f0f9bacca8d44e20bd0e21da819737aed0ff62b8)
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Probably we'll keep the Window and Screen example: it has walkthrough
docs already. Snippets can be used to illustrate some simplified
scenarios, while the example is a bit fancier.
Likewise, link to the Window and Screen example from the Screen docs.
Change-Id: I20c803affd1f4b6d44b41520782e5ad3c69fc871
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 36e3ea45f9df38ee0f2e1e619a8c344357d56896)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| |
| |
| |
| |
| |
| | |
Change-Id: I5b5c1663f626ce3bfe4c01edbc5480729a1b91f6
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 94475c9e533dc8b05c606c92b91ab2b645960ac0)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| |
| |
| |
| |
| |
| | |
Change-Id: I35ba013152628591d016c632828a1c4e64cf5978
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit 78d2cec488f8ab4ab45433ae9a9039f9cb7a5771)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- color groups are better shown with copyable monospace syntax rather
than capitalized
- clarify that using palette grouped-property syntax does not imply
that you must define every color
- Window has a palette property, inited from SystemPalette: it's
not only ApplicationWindow
- testable snippets
- reuse part of the windowPalette snippet for the Window.active
property (switching colors might be the main use case)
- make more links
Change-Id: I5974351ba66fc9aeec34cb6a4aba1eb85289f536
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit f1e7e1c3987b905157a1b9b418ea2649100eb390)
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt 6.2.9-lts release
Conflicts solved:
dependencies.yaml
Change-Id: If2cf4ac99b3e70b6a875b00cc4c3e7766b361a08
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- This started with QTBUG-112322: introduce the border property next to
the first snippet where it's used.
- Give declarative-scalegrid.png a white background rather than
transparent, to be consistent with the screenshots and to look better
with a dark documentation style.
- Make the snippets resizable so that it's possible to test the effects
of the horizontalTileMode and verticalTileMode properties.
- Get the borderframe.svg and .png files from the qtdoc repo (which
ought to have been in this repo already, but perhaps not).
- Resize borderframe.svg to 120x120 and set document size to match
(in Inkscape); this makes it possible to use the svg directly in
BorderImage, to test that QTBUG-25244 is really fixed.
- Make the snippets match the screenshots (all 182px wide, with grey
rectangle borders as shown).
- It seems our scaling is smoother (less jagged) than in the old
screenshots, so the new ones make a better impression.
- Add region index labels to snippets and screenshots to be a bit less
confusing next to the paragraphs that are talking about "parts of
image in regions 2 and 8" and so on. Too bad they have to be so tiny.
- Use \value rather than \li for enum values.
Amends 1a84b190bd1a2781d03f13fa43ab92bf34809041
Task-number: QTBUG-25244
Fixes: QTBUG-112322
Change-Id: I697ae1356eee62990b7903601cc493a04d3647a2
Reviewed-by: Andreas Eliasson <andreas.eliasson@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
(cherry picked from commit b26439b2cb8e90055b7a77d66dc0d8ad81734c27)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
tqtc/lts-6.2-opensource
Conflicts solved in a file:
dependencies.yaml
Change-Id: Ib4083daa41a689b937d2aeb522e93e3aab0be1c4
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Many of the inherited docs were inappropriate or insufficiently specific
to PointHandler. Now we have more snippets with more ideas for how it
can be used.
As a drive-by, fix a typo in the docs for
PointerDeviceHandler::acceptedPointerTypes and add a link to the new
PointerDevice page added in e283c05af745210d4a1f6c0aa9c33bf4da23a1e0
Fixes: QTBUG-74020
Fixes: QTBUG-106878
Change-Id: I028e1577ac5d4ef0b927c94259d6ab25b6028885
Reviewed-by: Doris Verria <doris.verria@qt.io>
(cherry picked from commit 4c6d0b2bf09329dd8b036761f8f2924f54af3a07)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
People are constantly confused by GesturePolicy and its default value,
so we really need a "glanceable" reference in the docs to show the
differences between use cases.
Also clarify the pitfalls with the default DragThreshold value.
We switch from the \value tag to a 2-column \table because the \image
would otherwise break the table, and also because it saves space and
acts as a meaningful reminder to have the animation right under the
enum value that is being documented.
Task-number: QTBUG-70397
Task-number: QTBUG-73262
Task-number: QTBUG-100534
Task-number: QTBUG-107239
Task-number: QTBUG-111310
Change-Id: I1ff45f58a8a8edf55f4a8696d881aa9e0bedcfe3
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
(cherry picked from commit a6e196ce9cd327df53ef9b9db3020f7775ee1754)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |/
|
|
|
|
|
|
|
|
|
| |
This reverts commit 74089697cf2a4961fb697100555b17ae2342d734.
Revert of commercial license headers is required for the
Qt 6.2.x opensource releases, Qt 6.2.5 onwards.
Task-number: QTBUG-107760
Change-Id: Id49069cb5e5f261da185fd082dfb71deb259d387
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some base class snippets use TapHandler, but it's better to show
snippets specifically with HoverHandler. These snippets are also
runnable and thus testable.
Fixes: QTBUG-95395
Task-number: QTBUG-101932
Change-Id: Ibcdc30ff8a785a3651177c79522332cf09c3013c
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
(cherry picked from commit a76ad7ef6a87af074612897ea6df30167ebe698e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated header.COMM to the files in tqtc-qtdeclarative.
Examples, tests, or documentation files are not updated.
The commercial license header may contain some
additional lines so that its line count equals with
the earlier license header. Reason for this is that
some autotests use hard coded line numbers and a
change in the line count causes failures in tests.
Task-number: QTQAINFRA-4941
Change-Id: I32f554b0a8cb527f74d46f3c02b0e745d9fc5ddf
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
Using REQUIRED as a prefix instead of suffix works better with
OPTIONAL_COMPONENTS, and is also the order in the CMake manual.
Task-number: QTBUG-98867
Change-Id: I021c8f0c7f886d8f7037a1dd92ef1e8d747a45f4
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit ad69aca9a6c2fdcc12bd6ecd55d2e417d1af6335)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It would be better to emit the whole pointer event (by pointer because
it's non-copyable, or make it copyable and emit by value), but we can't.
So we just add the button being tapped; more information is available
from the eventpoint argument and TapHandler's point property.
To avoid name clashes with anything that's already called "button" in
anyone's QML (which is quite likely, actually), the new signal argument
is unnamed, so that users will be required to write a function signature
that gives it a name rather than relying on context injection.
[ChangeLog][QtQuick][Event Handlers] TapHandler's tapped(), singleTapped()
and doubleTapped() signals now have two arguments: the QEventPoint instance,
and the button being tapped. If you need it, you should write an explicit
function for the signal handler: onTapped: function(point, button) { ... }
or onDoubleTapped: (point, button)=> ...
Fixes: QTBUG-91350
Task-number: QTBUG-64847
Change-Id: I6d25300cbfceb56f27452eac4b29b66bd1b2a41a
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 5864644ac8bc3c561696ffef5d033b1cab7d950f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
| |
Change-Id: I1f503cd03c35e48f2219e95db57b153c69badb0b
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 9fdb12bdac0efd9875b2d98ae82c3702cf722469)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
| |
It was ironic that it's the most obvious use case of TapHandler but
we didn't have some easy copy-and-paste code for making your own button.
Change-Id: I680b6f828f0df82e2ab8b434a2e76aabb21fc2b9
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
(cherry picked from commit 0fb1a49db192e7b0f0b0fe7ac441dead1608eb63)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Document the exclusive/passive grab concepts better
- Mention gesturePolicy's impact on grab behavior in the TapHandler docs too
- More links
- Add a couple of snippets illustrating simple use cases with handlers
- Don't bother mentioning Qt.labs.handlers anymore
Task-number: QTBUG-68110
Change-Id: I5e6f538c2bc8cafef679f535a5248b218b4a8068
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
(cherry picked from commit aade6857d12b2c9cd5552d25f4d084a5fcd25f7d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This shows how to use non-rectangular shapes for hit tests,
as well as how to define the contains function in QML.
Task-number: QTBUG-89380
Change-Id: I93c686d840b292816a788c05a0a76fafa338d5f8
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit 382d2bfe5f261c269ccf4b970c826003c90d57ae)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
| |
Fixes: QTBUG-94048
Change-Id: Ie80151381efe8f950e8a158f1aeb0dc5be154c64
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit 4bf29e799d1f949d384f8a16e49177363f2b2fe2)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
| |
Task-number: QTBUG-68078
Task-number: QTBUG-76310
Change-Id: Id7b971f5147474274200ef2fdd52ce21f8d60bdd
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 5971a6faaa1124f5ef3f0b42d4ed0298cf8096a3)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Fix up some minor issues in the documentation of
selection support in TableView.
Change-Id: Ica2c0014f4e7f960332c283c1ff83a6b0bdd7df2
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
(cherry picked from commit c60dc57dda052f800ac5ea16c208c2c70b366358)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for assigning a QItemSelectionModel to TableView.
By doing so, delegate items that has a "required property selected"
defined will get this updated according to the state of the
selection model.
It's essential that the property is defined as "required". If not, the
property will simply be ignored by TableView. This is done to ensure
that existing applications that already has a "selected" property
defined, will continue to work as before, unaffected by the new
selection API.
[ChangeLog][QtQuick] TableView now supports selections by using an
ItemSelectionModel.
Task-number: QTBUG-74750
Change-Id: I4f4d75e9e65563b9aab0c54f3aa4aad2f6883952
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Instead of sharing the animation, create an inline component for it and
instantiate it twice. Also, fix Behavior to actually apply to color.
Fixes: QTBUG-40851
Change-Id: I7dce5acb121ac6d699d782d24cc77ed9f0fa94e7
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Injected signal handlers are bad practice because they aren't declared.
Pick-to: 6.1
Task-number: QTBUG-89943
Change-Id: I3a691f68342a199bd63034637aa7ed438e3a037b
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Remove all qmake project files, except for examples which are used to
test that qmake continues to work.
Change-Id: Ic4abb72dc2dcd75df7a797c56056b6b3c5fe62ac
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
| |
As opposed to being local to the item's parent.
Pick-to: 6.0 5.15
Change-Id: Idcf2cdbedcac24a6890ce761c3f2a23f2c7a8dc4
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-73058
Pick-to: 6.0
Change-Id: Ie72c1f4331ad05f31d9a646730133c97c4b15790
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Assigning objects to signal handlers can be convenient, as seen in the
examples which use it together with ListView.onRemove.
However, that convenience makes it hard to reason about what actually
happens. Moreover, the only user of that functionality are the Animation
classes, and the usage of DefaultMethod is not documented anywhere.
[ChangeLog][QtQml] Assigning an object to a signal handler is deprecated.
Instead, create the object, give it an id, and call the desired slot
from the signal handler. For instance, instead of of
ListView.onRemove: SequentialAnimation {...}
use
SequentialAnimation {id: removeAnimation; ...}
ListView.onRemove: removeAnimation.start()
A warning will be printed whenever an assignment of an object to a
signal handler occurs. The warning can be controlled via the
qt.qml.defaultmethod logging category.
Change-Id: I001ddf4d7933871977f84a5e012d020fb043cc64
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
| |
Pick-to: 5.15
Change-Id: If63f4c59f18bc0754ce2e68e424f6efd0f512d30
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
| |
Fixes: QTBUG-83976
Change-Id: I307e96be0d3d2edeb8d9065d100c1ef38c8824c7
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
|
| |
|
|
|
|
| |
Pick-to: 5.15
Change-Id: I50facb06e37c26bf86d032d3fd5377f23a5d2bc2
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The two ShaderEffect related snippets are removed, with the relevant
code folded into the documentation itself. We cannot support standalone
snippets with custom shaders as we'd need to have separate shader files,
qsb files, scripts to build, etc. This is not reasonable at this point.
In layerblending.qml the ShaderEffect serves no purpose, apart from
providing a fancy background that is irrelevant to the topic. Just
remove that.
Change-Id: I726f029c8b7096938aa609031e391e9e57ef1655
Reviewed-by: Christian Strømme <christian.stromme@qt.io>
|
| |
|
|
|
|
|
|
|
| |
This also removes QQuickUniformAnimator, which is not yet ported
to RHI (QTBUG-83976)
Task-number: QTBUG-83977
Change-Id: I3e656e6817ac991371b7f6557f050e122635d279
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
This also means the RegExpValidator QML type will be gone. Use
QRegularExpressionValidator instead.
[ChangeLog][QtQuick][RegExpValidator] The RegExpValidator QML type has
been removed. Use RegularExpressionValidator instead.
Change-Id: If25fc5a258a669dfd28e705271757caa252ce05c
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
| |
|
|
|
|
|
|
| |
Use static registration, provide a .pro file, and make it load and show
the right file.
Change-Id: I949831a399ce00cd8b3d012d8bd4e95a1efcdeb5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
|
|
|
| |
Change-Id: I9e2c44ddcbb6c7e3a92b2bd7d2492ece0cd0e62d
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/plugins/qmltooling/qmldbg_debugger/qqmlenginedebugservice.cpp
Change-Id: I133bfd4bd9dd6f704252c956c90f05e8a8a40d6a
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This file was forgotten when moving the documentation to qtxmlpatterns,
leaving the docs broken.
Task-number: QTBUG-77176
Change-Id: I832a4c3cb2551b8e683b6e6fb97034ba86a74322
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
| |\|
| |
| |
| |
| |
| |
| | |
Conflicts:
src/quick/items/qquickitemview.cpp
Change-Id: Ib9faebdbef5eebb80f4e6aeb5b15b5df7494b157
|
| | |
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-81306
Change-Id: I8ee50727f4e75eee8c0997f17193d8c99e855551
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
|
| |/
|
|
|
| |
Change-Id: I6777eb179643ca2d5fb14f96f5f5ac02f5f2fb04
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were a lot of documentation warnings introduced by the
separation of QtQml.Models and QtQml.WorkerScript modules
from the QtQml documentation project into their own
sub-projects.
Fix the above, and also ensure that the experimental
Qt.labs.qmlmodels QML types are listed in the documentation,
and add them also on the QML module page for QtQml.Models.
A few warnings remain, they may be indicative of issues
not in the scope of this commit.
Fixes: QTBUG-79812
Change-Id: Idc25c976e4c96feab4aae893519d6c9245f57a64
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|