Currently the value types of e.g. layer.textureSize and layer.sourceRect
are only resolved for QML Item, but not QML Control. This patch
increases the recursion depth while collecting the attributes of values
types in order to be able to set layer.textureSize.width or
layer.sourceRect.x.
It also adds those attributes to be able to read the values.
Change-Id: I61ba1468d1443953f0a5b6ab2241114dc441bb79
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Instead of creating subclasses of ClangToolRunner configure
the base class according to the tool specifics.
Change-Id: I51b611b2375571453c7f9690499d744582f035c1
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: David Schulz <david.schulz@qt.io>
The dialog and main window variant of this wizard was broken since ever.
Generally two widget ui templates are generally confusing for the user,
so remove the broken wizard that promotes the not recommended way of
using ui files. Also we support the automatic conversion from ui to py
files nowadays via the PySide6 project tool.
Fixes: QTCREATORBUG-25807
Change-Id: I3ec6000a6c3fb076e3a54c70f3cccdd12df28701
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This change does not affect font files.
For all other assets, the file type is now also shown in tooltips
For image assets, the image size is also displayed.
Task-number: QDS-8177
Change-Id: Iceb93a0ffe1cb284a87cc93f1da2060f6f4f1529
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
All material types have a so called base color that determines the
diffuse color of the material, though the property is named differently
in different material types:
DefaultMaterial: diffuseColor
PrincipledMaterial: baseColor
SpecularGlossyMaterial: albedoColor
When changing a material type in material editor, if the base color
or the corresponding base map properties have been set, the values
are copied to the corresponding property in the new type.
Fixes: QDS-8738
Change-Id: Ia8e767ebf9b2d9026ff107e4245b37a788fd98d4
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This patch update tooltip text for 2D Geometry Section fields.
Fixes: QDS-8722
Change-Id: Id2db204057778fd141bbe17204e200d59070db8a
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Property name was changed on creator side when aux property handling
was refactored, but corresponding change was not done in puppet.
Change-Id: Iba21661908d6c46d7f586c18f0d34fcece597c9a
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Child nodes of a locked node should also appear locked, so they need
to be updated whenever locked state changes on a ancestor node.
Fixes: QDS-8732
Change-Id: I5675e129fb60c5ad8c0fdbc7e0a0a7fef410747a
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
... and re-use the old QtcProcess::readAllStandard* names for
a QString-returning 'decoded' version.
For now, only use that in 'full Utf8' cases, to stay bug-compatible,
the plan is, however, to employ the QTextCodecs we have already
in the channel buffers. That will be one-by-one, though.
Change-Id: Id209e0671920d4ea4197918e872f441254112d52
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
... to create SimpleTargetRunner runners for a single run config.
Change-Id: I8af3d7cdcaf54f0584af948aa6e0fa015d1a3077
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
When parsing remote .pro files the parsers needs to pretend it runs
on the remote device.
All internal data are now "local on the remote", so that string
manipulation in .pro files "just works", and a 'device root'
string is passed around to relevant functions which then use
it to construct FilePath::toFSPathString()-style paths that
our custom FSEngineImpl can then map to the real device.
Remote $$system() calls are intercepted by the local parser and
redirected using the usual QtcProcess mechanims.
Quite a bit of the ProParser needed adjustments, so there's some
potential for regression.
Task-number: QTCREATORBUG-28242
Task-number: QTCREATORBUG-28161
Task-number: QTCREATORBUG-28355
Change-Id: I6100e7aca4e1db35f5e9689004110aab57e2c595
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
