| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Task-number: QTBUG-14041
Reviewed-by: Aaron Kennedy
|
|
|
|
| |
Task-number: QTBUG-14089
|
|
|
|
|
|
|
|
|
| |
This property complements Component.onCompleted. It is emitted before
the destruction actually begins (for the most part) so the objects are
still alive and accessible.
The QtObject.onDestroyed signal is now blocked as it never really worked
properly anyway.
|
|
|
|
|
| |
Always use private/. The WinSCW compiler doesn't search the current
directory, for whatever reason.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changing value type bindings in state changes, and implicitly removing
them on property assignment was not reliable. Internally the system
considered a binding on "font" and one on "font.x" as a binding on two
separate properties, even though the "font" binding completely
overrides the "font.x" property.
Following this change a binding to "font.x" creates a proxy binding object
on the "font" property in addition to the "font.x" binding itself. This
allows behavior to be consistent across all operations.
QT-2920
|
|
|
|
| |
Author: Erik Verbruggen
|
| |
|
| |
|
|
There's nothing meta about our properties.
|