| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Add a future statement to all Python source files.
Task-number: PYSIDE-2786
Change-Id: Icd6688c7795a9e16fdcaa829686d57792df27690
Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After the new context manager is in place, most of
the examples benefit from moving QPainter into a
`with` statement.
The comments concerning PyPy could be removed, again.
[ChangeLog][PySide6] The examples are updated to use the new
context manager for QPainter.
Task-number: PYSIDE-535
Change-Id: Idf7e1f734d549ed663383ffbb2416297ebb1e0c7
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While testing the examples with PyPy, a number of examples
used QPainter without explicitly calling painter.end() and
crashed.
This works in standard Python, but leaves the painter open
in other implementations, because the implicit deletion of
objects when going out of scope does not work in the
wrapper when garbage collection is used.
Fixed by providing the missing painter.end() calls.
This problem should finally be fixed by making QPainter a
context manager. The same approach was taken by Python.org and
the file open/close functions. The context manager was needed
for implementations like IronPython, Jython and PyPy.
[ChangeLog][PySide6] The examples were adapted to PyPy's
need to close QPainter, explicitly. Eventually, we may turn
this into a context manager.
Change-Id: I18eeeff7df800bafce91a1e5c98c469aa3bcc41b
Pick-to: 6.2
Task-number: PYSIDE-535
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
| |
Task-number: PYSIDE-1112
Change-Id: Ifcb4da974bdcad7af536404fffdbffc585d3d167
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor and brush up the code to C++/Python naming conventions.
Turn text/running into properties.
Most importantly, fix it to not crash when the text initially
is empty.
Task-number: PYSIDE-1455
Task-number: PYSIDE-841
Change-Id: If94558a453b1824ba54bd4f94808ced5798b2dc3
Reviewed-by: Christian Tismer <tismer@stackless.com>
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
| |
Adapt CMake files, build scripts, tests and examples.
Task-number: PYSIDE-904
Change-Id: I845f7b006e9ad274fed5444ec4c1f9dbe176ff88
Reviewed-by: Christian Tismer <tismer@stackless.com>
|
|
|
This example is based on the WigglyWidget Qt/C++ example,
and shows two ways of using a Custom Widget:
* A full translation to Python, wigglywidget.py
* Exposing the widget via Shiboken.
The main.py file includes both scenarios and display them.
Task-number: PYSIDE-841
Change-Id: I53c6db540aae2d5672a96bcf8f0e4a3e06b7ce9e
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
