| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
subdirectories to make it easier to locate examples for certain
features (e.g. animation) and to distinguish between different types
of examples (e.g. very basic examples vs complex demo-like examples).
|
|\
| |
| |
| |
| | |
Conflicts:
examples/declarative/dynamic/qml/itemCreation.js
|
| | |
|
|/
|
|
|
|
|
|
|
| |
For graphical objects (the common case) a common mistake is to not
parent a dynamically created item. Since you almost always want to add a
parent, and it's hard for a beginner to diagnose this problem, a parent
is now a required argument and dealt with by the createObject function.
Task-number: QTBUG-10110
|
|
|
|
|
|
|
| |
The Component status enum covers all of these properties already and
removing these also makes the API consistent with Image and Loader.
Note this change only affects the QML Component API; the methods are
still available for QDeclarativeComponent.
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Also updated examples to still work, and the dynamic example now uses
exceptions a little, to demonstrate that it can be done. Exceptions are
also now filled out with the QML error data.
Task-number: QT-2801
Reviewed-by: Aaron Kennedy
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Inline blocks/includes have been replaced with an import syntax:
import "foo.js" as Foo
this gives better separation between QML and code. Imported script blocks
also have a mandatory qualifier, which leads to better optimization
potential.
|
|
|
|
| |
Task-number: QT-2846
|
| |
|
|
|
|
|
| |
The code is now a bit on the imperative side, but that was the
only working solution to remove the binding loops.
|
| |
|
|
|
|
| |
Dynamic property creation appears to have been restricted.
|
|
|
|
|
|
| |
This attribution is not necessary anymore since 923710196d6d5...,
Reviewed-by: Michael Brasser
|
|
|
|
| |
working Z and items can no longer be placed in the sky (due to scaling).
|
|
|
|
| |
SystemPalette.
|
| |
|
| |
|
|
|
|
|
|
|
| |
createComponent() and Component{} are now the same, and so Component{}s
can now be passed around for use in script.
Also this commit fixes the minor bug QT-2386
|
| |
|
|
|
|
|
| |
Includes adding a comment to the positioners to alert others that you
shouldn't use anchors as well.
|
|
|
|
|
| |
Task-number: QT-2270
Reviewed-by: Yann Bodson
|
|
|
|
|
| |
The mouse is no longer at 0,0 of dragged item, but rather at the same
point as the original click.
|
|
|
|
|
|
| |
The example is nearly done, just needs a little more aesthetic
transfiguration. Also this commit introduces some generic components
that could be easily used to make a game like ktuberling.
|
|
|
|
|
|
|
| |
The start of a prettier version. Not yet complete, does not full resolve
the task.
Task-number: QT-2270
|
|
|
|
|
|
| |
Had some accidental global vars
Task-number: One of the QT-2270s
|
| |
|
|
|
|
|
|
| |
SetProperties -> PropertyChanges
RunScript -> StateChangeScript
SetAnchors -> AnchorChanges
|
| |
|
|
|
|
|
|
| |
Also updated dynamic example to have a fadeout effect on deletion.
Also slipped in a toStr function, as it didn't work when I called it
toString.
|
|
|
|
|
| |
Adjust examples and demos accordingly.
As per QT-558
|
| |
|
|
|
|
|
| |
Wasn't actually loading the object's context properly, with regard to
url resolution.
|
|
|
|
|
|
|
|
| |
Renamed evalQml to be consistent with us, not javascript.
Fixed bug where createComponent never had the right path.
createQmlObject (evalQml) now has a parent as a argument.
It also still has a bug where that parent doesnt get set properly,
although it is used as the creation context also.
|
|
|
|
|
| |
Adds some error handling, and cleans up documentation and the example
a little.
|
|
|