| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
We are now checking that the QAction is not related
to the About or Quit button on Mac OS X
Task-number: QTBUG-7540
Reviewed-by: Morten Sorvig
|
|
|
|
|
|
| |
The signal handling bypasses the public QScriptValue API (it
calls JSC::call() directly), hence we need to insert a shim to
make sure that the correct identifier table will be used.
|
|
|
|
|
|
|
| |
Another side effect of
62c72ed2fd4aa6f5e62a190abf2dde2ba0f5ff0b .
Task-number: QTBUG-9262
Initial-patch-by: Jarek Kobus <jkobus@trolltech.com>
|
|
|
|
| |
open is public.
|
|
|
|
|
| |
Apparently it's possible that the window has been shown but
haven't received a paint event yet.
|
|
|
|
| |
Also describe its purpose in the example doc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QScriptEngine::reportAdditionalMemoryCost(int).
This function provides the ability to give a hint to the engine
that it should perhaps trigger garbage collection sooner rather
than later.
For example, if you've implemented a JS ByteArray class that
wraps a QByteArray, and a user constructs a few hundred
temporary ByteArray objects of large sizes, failure to report
the additional memory cost may cause the application's memory
consumption to grow and grow (because the script engine thinks
they are "cheap" objects, the GC won't kick in).
Reporting the correct size can be difficult (or impossible) in
some cases. For example, it's difficult to predict the total
amount of system memory & resources consumed by a QImage.
But even reporting a heuristic / approximate cost can be better
than reporting no cost.
Task-number: QTBUG-6238
Reviewed-by: Simon Hausmann
|
|
|
|
| |
Reviewed-by: Morten Sorvig
|
| |
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
demos/declarative/minehunt/minehunt.cpp
src/declarative/qml/qdeclarativecompiler.cpp
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
4.7-integration
* '4.7' of scm.dev.nokia.troll.no:qt/qt-multimedia-staging:
Rename loopCount to loops, in line with other declarative elements.
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Dmytro Poplavskiy
|
| | |\ \
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* '4.7' of scm.dev.nokia.troll.no:qt/qt-qml: (76 commits)
Qt.Infinite -> Animation.Infinite
Doc fix.
Skip tests for now
Make autotest work on windows.
Remove faulty assert - the precondition is checked for correctly later on
Ensure currentIndex is updated when items inserted before currentIndex
Replace Animation's repeat property with loops.
Fix compile in namespace.
Compile with qtnamespace
Disallow the implicit QDeclarativeGuardedContextData copy constructor
Doc
Fix leak.
StateChangeScript doc.
A StateChangeScript should never be run when leaving the state.
ScriptAction doc.
Rename stateChangeScriptName to scriptName.
Doc
Document QML security considerations.
Fix flicking views at boundary with StricthighlighRange
Fix abort in flipable
...
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Too misleading to have on the Qt object, as it only means infinite
for animation loops.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |\ |
|
| | | | |\ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
You can now loop a fixed number of times as well as forever. The old
repeat behavior (loop forever) can be acheived with loops: Qt.Infinite.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Was occurring when items inserted but no items had been created yet.
Task-number: QTBUG-9313
|
| | | | |\ \
| | | | | |/
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
src/declarative/util/qdeclarativexmllistmodel.cpp
|
| | | | |\ \ |
|
| | | | | | | |
|
| | | | |_|/
| | | |/| |
| | | | | |
| | | | | | |
Task-number: QTBUG-9336
|
| | | | |/
| | | |/| |
|
| | | |\ \
| | | |/ /
| | |/| |
| | | | |
| | | | | |
Conflicts:
src/declarative/qml/qdeclarativecompiler.cpp
|
| | | | |
| | | | |
| | | | |
| | | | | |
Task-number: QTBUG-9312
|
| | | |/ |
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tests/auto/declarative/qdeclarativedom/data/importlib/sublib/qmldir
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For a Transition running in reverse, stop ScriptAction from running any
StateSchageScripts.
|
| | | | | |
|
| | | | | |
|
| | | |\ \ |
|
| | | | |\ \ |
|
| | | | | |\ \ |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Currently, this feature too prone to accidental misuse and abuse.
|
| | | | | | | | |
|
| | | | | |/ /
| | | | |/| | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Flipable was calling updateSceneTransformFromParent, but this can only
called when the the parent's scene transform is guaranteed to be updated,
which is not the case in flipable.
Task-number: QTBUG-8474
Reviewed-by: bnilsen
|
| | | | | | | |
|
| | | | |/ /
| | | | | |
| | | | | |
| | | | | | |
Task-number: QT-2831
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously we were not outputting those that occurred on
component->create().
|
| | | | | | |
|
| | | | | | |
|