| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
QTBUG-9726
|
| |
|
|
|
|
| |
QTBUG-9799
|
|
|
|
| |
QTBUG-9704
|
|
|
|
|
|
| |
In QML "var"s are not the same as JavaScript vars - they are QVariants
instead. However, as they behave in a similar enough fashion to native
JavaScript it can be confusing to developers when they are called "var".
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QML used to silently ignore a log of errors - such as a failed assignment
to a QObject property. These errors are now all reported as exceptions
in JavaScript.
Other questionable activities, like assigning a JavaScript array to a
"property var" property which appeared to work, thanks to QtScript's
transparent conversion of arrays to a QVariantList, are now blocked
entirely.
QTBUG-9152 QTBUG-9382 QTBUG-9341 QTBUG-6886
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
There's nothing meta about our properties.
|
| |
|
| |
|
|
QDeclarativeXXX.
|