| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Pick-to: 6.8
Task-number: PYSIDE-1735
Change-Id: Ic2c478ef363d73f65f366e21529c0429c86539aa
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the API limitations, we have to ensure that the engine is deleted
before other parts of the application is deleted. Otherwise exposing
objects using setInitialProperties() or setContextProperty() for example
will cause warnings to be printed. It is a good practice to always
delete the engine manually so all the code should be consistent.
Task-number: PYSIDE-1612
Pick-to: 6.8
Change-Id: I01f16359e9d90cefd5957708fe12ce489bd7edc0
Reviewed-by: Jaime Resano <Jaime.RESANO-AISA@qt.io>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
- This tutorial expands on part1 by integrating SqlAlchemy with PySide6,
by storing the data in a SQLite database.
Pick-to: 6.8
Task-number: PYSIDE-2850
Change-Id: I195149bd861b1fb1a25623a9fe05e42f1e85054c
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
|
|
|
- Example that extends on the Finance Manager application from Part 1
to use a SQLite database to store the data, thereby showing the
how to use SqlAlchemy with PySide6.
Pick-to: 6.8
Task-number: PYSIDE-2850
Change-Id: I2cce6d033812796ea2fe5cc200c1854494a308f5
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
|
