| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
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".
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This commit deletes the uneeded classes/declarations since we have now
an inline support for QGraphicsObject based classes. QGraphicsLayout
bindings works the same way because the layout property has been added
to QGraphicsWidget. The only feature that is missing for now (because
of the deletion of GraphicsObjectContainer) is the anchoring support.
We will probably take a look on how to support this feature properly
with no wrapper.
Task-number:QTBUG-9456
Reviewed-by:Michael Brasser
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The TextInput has support for scrolling now so it's quite usable.
You can deactivate the auto scrolling with a property if you want to
do crazy animation while scrolling. This commit also fixed several bugs
with the current implementation especially regarding aligments : selection
was broken, moving the cursor also -> fixed. I have also added a tiny fix when
the TextInput lost the focus -> the selection is cleared.
Task-number:QT-2745
Reviewed-by:Michael Brasser
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In shadow build environments, we cannot enforce that shared
library objects for plugins are located in the same directory
as the qmldir file. This makes it hard for Creator to support
mixed projects (qml/c++).
In order to gain more flexibility, the patch introduces a
pluginPathList to QDeclarativeEngine, which completes the existing
importsPathList.
The pluginPathList defaults to ["."], which indicates the directory
where the qmldir file is located in.
The qml viewer tool gains a command line option -P to add to the
pluginPathList.
For consistency, the -L option ("Library") has been renamed to
-I ("Import"). QDeclarativeEngine::importExtension() has been
renamed to QDeclarativeEngine::importPlugin().
The documentation has been adjusted accordingly.
Done with erikv.
Reviewed-by: erikv
|
| | | |
|
| | |
| |
| |
| | |
Task-number: QTBUG-9701
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
QTBUG-9538
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Task-number: QTBUG-9692
|
| | |/
|/|
| |
| | |
Task-number: QTBUG-7568
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The SmoothedFollow is the same as the old EaseFollow, so it's not an
animation, but its main use case is to be used as a property value
source to automatically follow the 'to' property, as in the example below.
Rectangle {
color: "green"
width: 60; height: 60;
SmoothedFollow on x { to: rect1.x - 5; velocity: 200 }
SmoothedFollow on y { to: rect1.y - 5; velocity: 200 }
}
This element shares the internal implementation with SmoothedAnimation,
both providing the same easing function, but with SmoothedFollow it's
easier to set a start value to animate intially and then start to follow,
while SmoothedAnimation is still convenient for using inside Behaviors
and Transitions.
Reviewed-by: Michael Brasser
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
The QWidget destructor is largely a copy of the QObject destructor.
QML shutdown occurs in a slightly different order in this case.
|
| |
|
|
| |
Caused crashes in various test cases
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
wrap remains for a little while, and will produce a warning.
|
| | |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 973cfce37fcdd1ce330f237eaa76930db55a73f6.
Need more consideration before adding modelReset(). For example if
item insertion/removal is supposed to trigger animations through
added/removed signals, they won't be triggered if only the modelReset()
signal is emitted. Also if we add modelReset(), it should also be
implemented for ListModel to make sure it is implemented by all subclasses
of QListModelInterface and to test the impact of this on the view classes.
|
| | |
| |
| |
| | |
Task-number: QTBUG-6332
|
| |\ \
| |/ |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 9d9161446bfad883c298d54a122e822c5e273a9c.
This was a bad idea. It complicates the "property var" are not really
JavaScript var problem. Some of the patch is valid, and it will be
applied separately.
|
| | | |
| | |
| | |
| | | |
Task-number: QTBUG-9371
|
| | |/
| |
| |
| | |
Task-number: QTBUG-9676
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We already supported returning QList<QObject*> from methods, but there
wasn't really much that could be done with the return value. This closes
the loop on QList<QObject*> support by allowing them to be properties,
and used as models.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also ensure warning is issued regardless of the order both pointSize
and pixelSize are set in the same item.
Task-number: QTBUG-9665
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(was done for builtins/plugins, but now also for qmldir-specified content)
Task-number: QTBUG-9627
|
| | |/
|/| |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
| |
QDeclarativeScriptClass only existed to make compiling against 4.6 and
4.7 easier.
|
| |
|
|
| |
QTBUG-6082
|
