| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
| |
Amends df87bd0d6c55e0ab11aa68f7db99337860134510.
Task-number: PYSIDE-2095
Pick-to: 6.3 6.4
Change-Id: I0a18abc35b1f6519fd8b82f98410240d8907652d
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Signals were not aware of new enums.
Worse, the name of the metatype was changed in Python.
Added a test that simulates the example.
Change-Id: I80e1f220c387ab39e918bfc63d6bb5cab6025590
Fixes: PYSIDE-2095
Pick-to: 6.3 6.4
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
State CMake 3.18+ and Python >= 3.7
Task-number: PYSIDE-2091
Pick-to: 6.4
Change-Id: Iad906a48bf4378ceeeebe5a55aeaa3f27ea0a61f
Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
| |
Fixes: PYSIDE-2088
Pick-to: 6.4 6.4.0
Change-Id: Ib571f67117403881001b51b1fda573074aa3fefc
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
| |
|
|
|
|
|
| |
[ChangeLog][PySide6] QtSerialBus has been added.
Change-Id: I661912279fa03b51d19483b603fff830ede225a9
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the right function to strip the qualifications from
the type since <const Pointee> and <Pointee> are treated identically.
Fixes a regression introduced by change
a262e9bae5dbdef92d5caa0e058a1ad07fa974d3.
This is in principle tested in the smart binding test, but
occurs depending on the order the types are seen, so, add another
test.
Fixes: PYSIDE-2071
Pick-to: 6.3
Change-Id: I838b1ae1dd607095b41018c973093a380f51ab6b
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes every PyEnum feature of PySide optional.
It allows to test the whole functionality.
Some flags might also make sense for people who cannot use the
new enums without modifications.
Maybe this should be there for now for internal use, only.
The flags for PYSIDE63_OPTION_PYTHON_ENUM are (hex)
1 (True) the default for PySide 6.4, full implementation
2 turn all Enum into IntEnum and Flag into IntFlag
4 re-add shortcuts for global enums
8 re-add shortcuts for scoped enums
10 don't fake shortcuts (forgiveness mode)
20 don't fake rename (forgiveness mode)
40 don't use zero default (forgiveness mode)
80 don't allow missing values in Enum
A startup setting of for instance PYSIDE63_OPTION_PYTHON_ENUM=6
should work in most cases, avoiding the fall-back to old enums.
Task-number: PYSIDE-1735
Change-Id: I636c4d9f8e671f5185058820605da73f688c16b0
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch supplies a _missing_ function to every (Int)?Enum
class that creates the given integer as a nameless enum.
The missing object is created on-demand and kept in the dict
"_sbk_missing_" for re-use.
[ChangeLog][PySide6] New Python Enum/IntEnum now allows for missing
values like the Shiboken enums before, increasing compatibility.
Task-number: PYSIDE-1735
Task-number: PYSIDE-841
Change-Id: I436b536e0a29337663cc3bca5db4322d9cf0de74
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Change the directory structure to closer match that of Qt.
Task-number: PYSIDE-841
Change-Id: I87aca346b6654aafe94dd1fb83c184c182ceb2e6
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
The function is exported, but not declared in Qt; requiring some
declarations.
Fixes: PYSIDE-2059
Change-Id: I682483553ea1a46b978f57e991cabe4b303607f3
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-89564
Change-Id: Iee2e2ac1acc608c746f84e9a28295b0016a4deed
Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Comparing a QtCore.Qt.Flags object with any other object calls the
PySideQFlags_tp_richcompare() function. This function always threw a
TypeError when comparing to a non-numerical object, causing undesired
effects. Account for these cases now by returning True or False if the
compare operator is != or ==, respectively.
Pick-to: 6.3 6.2
Fixes: PYSIDE-2048
Change-Id: Ic81a65ace743b57e90ffe7883e42eb8330b78832
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
| |
Change-Id: I00073b583c8c84e764a8693b50af44b3b91d55eb
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
QValue3DAxisFormatter::gridPositions(),
QValue3DAxisFormatter::labelPositions(), and
QValue3DAxisFormatter::labelStrings() return non-const-references to
lists for modifications. In PySide, add setters for them.
Task-number: PYSIDE-2025
Change-Id: I90f788962380eb2ff95736b33533c1c09b59fdce
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This enables using "QVariant", which is needed for QML.
Amends aae2f599e8215e49747c9b5dce698d35b913c6c7.
Remove a left-over qDebug().
Task-number: PYSIDE-1898
Change-Id: Ibbb543cfe582eba5d652dc180191c2741730c4e6
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
The new QKeyCombination calls are implemented for the
new enums, only. Add a @skipUnless
Explicitly no pick because 6.3 has that fix.
Task-number: PYSIDE-1735
Change-Id: Icf154fe9c3334e6f18ffc5dc675ed01c651785f5
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After turning IntEnum into Enum, a few classes need more
attention because the simple int coercion is no more
sufficient. Instead, a bit of help is necessary to make
the usage of the __or__ operator consistent, again.
On first sight, this coercion to KeyCombination looks slightly
unpythonic. But this originates in the complex matters. If you
observe what types are actually added, this is very correct.
Using the IntEnum version instead is not better. It is just
hiding the ongoings by using int, which would also allow
to combine two characters as a bad side effect.
[ChangeLog][PySide6] PyEnum now handles QKeyCombination correctly
with "|" or (deprecated) "+" operators, without falling back
to using IntEnum.
Task-number: PYSIDE-1735
Change-Id: I08b93b8b7ece75ca650f2916ec6f6f5bb711a70b
Pick-to: 6.3
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In QFormLayout::getItemPosition() on the C++ side, *rolePtr is not set
if row == -1, in which case on the Python side this gets converted to a
random value outside the enum range. Fix this by setting *rolePtr to a
default value in the glue code.
Pick-to: 6.2 6.3
Change-Id: I0c67c771ed017f14b211fa6ccf9c89706152d214
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The struct TakeRowResult was not explicitly declared in the
typesystem, leaving out some QFormLayout functions like
QFormLayout::takeRow(...).
Fixes: PYSIDE-1312
Pick-to: 6.2 6.3
Change-Id: I77577cb54ff9cca56435b62c4848832e79f575f8
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The signature tests were disabled for a long time.
Meanwhile, a number of unresolved values have piled up.
The reason was partially a weird mixture of intents that
made it unpractical to run the full tests on every platform.
Mamely, macOS was quite unclear about which signatures
have to exist and which don't.
This overhaul does the following:
* The various Shiboken modules were removed from the tested
signatures
* A pure test is added that only checks for no offending lines
As effect, signatures are tested unconditionally without any
other conditions. The other tests remain disabled.
Task-number: PYSIDE-510
Change-Id: Id9e65ed7324a795966f460e13dd95fd5cebcca6a
Pick-to: 6.3
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The mentioned check-in had a bug in the new enum conversion.
This will not be cherry picked but directly fixed in 6.3 .
Task-number: PYSIDE-1735
Change-Id: Ib9d7293e94baeeb7286e4b207fe73863fc8f5ac6
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was "PyEnum: Write a default Int decisor for Enum and Flag".
Historically, C++ enums were all compatible with int.
The new Python enums are more diverse here. There are the
basic types Enum/IntEnum and Flag/IntFlag.
We have tried a lot to come up with a sensible default heuristic
computed from the data. In the end, this was reverted and replaced
by a fixed list that was collected from similar implementations.
By the move away from Int inheritance, a few classes needed extra
support. Python 3.11.0b5 also required the Flag creation parameter
"boundary=KEEP". It is not clear if this is correct, yet.
[ChangeLog][shiboken6] Most former IntEnum/IntFlag are replaced
by pure Enum/Flag classes in a generally compatible way to other
implementations.
Change-Id: I1dbe7b0556a3375df89eb40e9d9f495f14bf42b1
Pick-to: 6.3
Task-number: PYSIDE-1735
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most PyEnum types will no longer be compatible with int, when we change
from IntEnum to Enum.
This has a number of consequences and leads to improvements
in type representations.
The repr of QKeySequence was actually wrong and misleading,
see the test qkeysequence_test.py .
We change the repr and the indexing to return QKeyCombination like
our competitor does since a long time.
[ChangeLog][PySide6] QKeySequence returns now QKeyCombination instances
when indexed and the new PyEnums are used.
Change-Id: Idaaeb44ca3b6103b3e0416eaeb691ad954745f73
Pick-to: 6.3
Task-number: PYSIDE-1735
Fixes: PYSIDE-2021
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
| |
Force the named arguments code to be generated for constructors of
QObject-derived classes in QtWidgets.
Fixes: PYSIDE-1986
Change-Id: Ibc04959091c55a51aa77021f71786ff927f78fb3
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The function return varying numbers of return values in an array. Add
a helper function to determine the number. Depending on it, a single
value or a numpy array is returned, matching the behavior of PyOpenGL.
Task-number: PYSIDE-2013
Task-number: PYSIDE-2017
Change-Id: I8a91e491939e668932ea03eda64d83ed08ab28b3
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a long existing bug in the PySide build system that
had a weird effect on macOS:
* building PySide with Limited API and testing worked fine.
* building PySide without Limited API worked fine too, but gave
crashes when testing pysidetest. It appears that macos
duplicates a static Python build, one of them uninitialized.
After a month with no solution, a Linux build had problems, too,
but complained already in the build.
It was solved by passing `--enable-shared` to the Python build.
This `--enable-shared` solved the macOS problem as well.
Further analysis by Alexandru led to the suggestion that the
Python libraries in pysidetest are not needed at all, and by
removing them, the whole problem went away.
This is now confirmed on other platforms as well. The option
`--enable-shared` is no longer needed in any configuration.
The problem was caused by 22e359bc19daf19033332aa2d7bb9726c7f4be14
from 2020-02-18.
Task-number: PYSIDE-1735
Change-Id: I08b8628e75ef9c664be30200ae295cd2e6004370
Pick-to: 6.3
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the new forgiveness, all the "normal" uses of old enums
are working with the new enums, too.
What does not work are range violations and inheritance of enums
from other enums.
Also, the implemented trick does not work for enums which
do not belong to a class. The induced bugs are easy to find,
because they should normally break at import time.
[ChangeLog][PySide6] The new forgiveness mode of Python enums
allows to use old enum code, most of the time. Much changed
test code was reverted.
Change-Id: I9c081831309f1b2358fe86e6107b0f4d78fd48cf
Pick-to: 6.3
Task-number: PYSIDE-1735
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch supports to write
Qt.Alignment()
instead of
Qt.AlignmentFlag(0)
Also supported is
Qt.AlignmentFlag()
which is mapped to
Qt.AlignmentFlag(0)
This trickery was quite involved since the Python opcodes
needed to be analyzed if we have a parameterless call.
Only in that case, we insert a partial object which supplies the
missing value=0 default.
Changing the implementation of PyEnum was not desired because this
is highly complicated, not portable and even not possible.
The change has been tested with Python 3.6 to 3.11.0b3 .
[ChangeLog][shiboken6] The new Python enums are made as compatible
to the old ones as possible. It is again allowed to use Qt.Alignment()
instead of Qt.AlignmentFlag(0), and a default of 0 is always allowed.
Change-Id: If6a93f8210ff6cae4e38251420e1ad5fffbe42cb
Pick-to: 6.3
Task-number: PYSIDE-1735
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a silent change in PyEnums that turns Enum attributes
into properties. This does not harm the Python interface but
needed some change in the duplication emulation.
Furthermore, new internal enums are created with an underscore name.
The meta class was changed from EnumMeta to EnumType.
[ChangeLog][shiboken6] The new Python Enums are now compatible with Python 3.11
Change-Id: I3b1ab63dc5eed15a75ebd0f42dddf4001f640c00
Pick-to: 6.3
Task-number: PYSIDE-1735
Fixes: PYSIDE-1960
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
| |
Adapt to qtmultimedia/c403e775f60a5d02e761904342ac243be1f22597.
Change-Id: Id078b2a7ca46ff775fbbc543428a3208d5410981
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When implementing Python enums, the behavior of old Qt enums
was copied: Every enum was also inserted into the enclosing scope.
This patch removes that for two reasons:
- it is inconsequent to keep an old quirk when we have all
enums renewed so much
- It is more consistent compared to our competitor
- it is a prerequisite to implement efficient lazy initialization
PROBLEM: Many constants (about 110) are no longer recognized, for
instance `Qt.AlignLeft` should be `Qt.AlignmentFlag.AlignLeft`.
The question is if that can be fixed easily in C++, or if
the file mapping.py should get ~100 new fixes?
SOLUTION: We allow the old enums, but tell nobody that they continue
to work. They also are not advertized in the PYI files.
[ChangeLog][PySide6] The duplication of enum values into the
enclosing scope, allowing to write Qt.AlignLeft instead of
Qt.Alignment.AlignLeft, is still implemented but no longer
advertized in PYI files or line completion.
Task-number: PYSIDE-1735
Change-Id: I79a90d08f2a5a3a069fa551e60d609ecad718239
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
| |
Change-Id: I9b58e806019ee7294da466a5fce1f1b7ed01c8a3
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Testing should always work for every allowed subset of modules.
We therefore include a check if Qml was compiled.
Amends d78151f89b2c374af366bee536c8ceeae3b2ab5e
Change-Id: I7b4a7eab7a4adcec8609b05b772b03e07c2117ab
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QEnum was implemented with Python enums, as opposed to the
old C++ enums. Now that support for Python enums is built
into PySide, it is necessary to keep the implementing
Python modules always the same.
This patch prepares QEnum and PyEnum compatibility for the
upcoming embedding of old enum implementations.
As a side effect: Python 3.6 and 3.7 had a hard-to-find
refcount error when creating new enums.
Task-number: PYSIDE-1735
Change-Id: Ic44459c8e319d6d0308c7366beafa6fe7df41b79
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- pyside6-qml is a tool that mimics the capabilities of qml utility and enables
quick prototyping for qml files. Most cli options of the qml tool are carried
forward to this tool.
example-usage:
pyside6-qml -a gui examples/declarative/editingmodel/main.qml
To see all the cli options available with this tool, do:
pyside6-qml --help
Task-number: PYSIDE-1878
Pick-to: 6.3
Change-Id: I98bd77ccf6a0a286bb54da264312e81bf2964dc7
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
| |
Pick-to: 6.3
Fixes: PYSIDE-1947
Change-Id: I9e1799f245b8d75f61ad9551cb847994ea59bdb9
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
| |
Task-number: PYSIDE-1735
Change-Id: Id51ee6dccdf3cc27ee851773f3482f3a6173b364
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Replace the current license disclaimer in files by a
SPDX-License-Identifier. Files that have to be modified by hand are
modified. License files are organized under LICENSES directory.
Task-number: QTBUG-67283
Change-Id: I065150015bdb84a3096b5b39c061cf0a20ab637d
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
bug_462.py had a precedence bug that was fixed in 6.3, already.
e must fix it here because the check-in was done already.
Explicitly no pick-to.
Task-number: PYSIDE-1735
Change-Id: Iaebd53e566bdfd73d2761268b3691f35c2f9de7c
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These tests are now completely identical to the old tests
and have an adapted Python Enum version if suitable.
Both versions can be selected once at runtime.
Having both test versions available as a runtime option
is a nice feature that really helps understanding the
consequences of the PyEnum move.
[ChangeLog][PySide6] The QEnum tests are enabled for both the
old Qt Enums and the new Python Enums.
Change-Id: I78a7473f4a86f8d2115acc56e4ed11cf135eb000
Pick-to: 6.3
Task-number: PYSIDE-1735
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
| |
- added tests for the setCookieFilter(...)
Task-number: PYSIDE-1912
Pick-to: 6.3
Change-Id: I484725072195846e7777fc577d167ff9ed374d59
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This effectively undoes 36431b071095b8999347df87621bf23ffcc2ac3d
which disabled numpy support in libpyside due to
- break cx_freeeze
- Cause embedding applications to fail to load with "undefined symbol: PyExc_RecursionError"
Auto-detection along with --enable/--disable options is introduced
instead.
All numpy code is now located in libshiboken and it cleanly recovers
when numpy cannot be found on the target system. The
PyExc_RecursionError issue could not longer be reproduced.
[ChangeLog][PySide6] Numpy support is now enabled by default.
Task-number: PYSIDE-1924
Change-Id: I0fdb3612471971afa49ac3141845cf5d6dbfa7e0
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Introduce an internal type QGeneric(Return)ArgumentHolder which casts
to QGeneric(Return)Argument and stores a QMetaType along with a data
pointer. It is returned by Q_ARG/Q_RETURN_ARG and then handled in
QMetaObject.invokeMethod().
Fixes: PYSIDE-1898
Change-Id: I229cb03d5d71c3b32a2e1eb4040f7641b8e49000
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds functions like QImage::toHBITMAP()/toHICON(), QRegion::toHRGN().
Treat them as plain PyLong types in order to be compatible with
PyWin32.
[ChangeLog][PySide6] Windows handle types HBITMAP, HICON and HRGN
have been added.
Pick-to: 6.3
Fixes: PYSIDE-1859
Change-Id: I07a98ecdd3da52ff0b0b78db56388f579ede3e46
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- added tests for the macros
Only 'void debug(const char *msg, ...) const' was considered among the
overloads in QMessageLogger. For more info, see the comment section of
the related issue PYSIDE-1899
Task-number: PYSIDE-1899
Pick-to: 6.3
Change-Id: Ie9a28abde8556f84736de75cf4b914002094c768
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Currently mainly used for testing, but might be generally useful.
Task-number: PYSIDE-1898
Change-Id: Iffc63048d3d520def79b4bae7d08a31829bea2e5
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
| |
Pick-to: 6.3
Fixes: PYSIDE-1921
Change-Id: Id80f9c2f7533d7e2d58af0fb0f1d6d8eb586d31a
Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Helps for hierarchies that do not have virtual destructors where the
default typeid(t).name() does not work (QStyleOption).
Pick-to: 6.3
Fixes: PYSIDE-1909
Change-Id: I9ce3769a8c3550d011023597eede0ae6f8c9ad68
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The __feature__ tests need a stronger way to reset the
feature selection reliably. Some cross-talk was observed
when running multiple tests together with PyTest. This
effect was hidden because our unit-tests are isolated in
individual processes by CTest.
- Remove all special 0x80 cases of TearDown functions
- introduce a new feature module function `reset` that
completely uninitializes the features, including the
`pyside_feature_dict`.
- drop the artificial naming of `__feature__` in favor of
`feature`. This is less confusing for people examining
the implementation.
[ChangeLog][PySide6] Feature switching was improved by avoiding
cross-talk between multiple test runs.
Task-number: PYSIDE-1019
Change-Id: I28550f293763ac58df72b8ce5c0a613c2067f6ba
Pick-to: 6.3
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
Pass the length to QString::fromLatin1().
Amends b90acad7ebd389b34465504d229552af6c8196e5.
Pick-to: 6.3 6.2 5.15
Fixes: PYSIDE-1895
Task-number: PYSIDE-1882
Change-Id: Ie829e479ad4e81f691cd3564ce1640175d1cdc32
Reviewed-by: Christian Tismer <tismer@stackless.com>
|