| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Commit eea84818e98af917d3cf2bf04ea17a416ef9d55e corrected some spelling
mistakes, one of which this test was relying on.
Reviewed-by: trustme
|
|
|
|
|
|
|
|
| |
It's the scene itself that acts as a focus scope, not the top-level
item.
Task-number: QTBUG-12682
Reviewed-by: Aaron Kennedy
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-12649
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
|
|
|
|
|
| |
SpringFollow was turned into SpringAnimation so it could be
used inside a Behavior. This patch completes the work and makes
it usable inside a transition.
This is the documented behavior of SpringAnimation, the patch
is essential to make SpringAnimation work consistently.
Reviewed-by: Michael Brasser
Task-number: QTBUG-12141
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-12142
Reviewed-by: Warwick Allison
This patch brings ability to switch QML Viewer's orientation between auto-orientation (=follow sensor),
portrait and landscape orientations (lock orientation) on Symbian. It provides same orientation options as
Qt Creator 2.1's Qt QML Standalone Application creation wizard. Also, menu item rotateOrientation now
works on Symbian, but it's hidden when orientation mode is set to auto-orientation.
Property runtime.orientation has been switched back to supporting four-way orientation on Symbian, previously
it only updated values between portrait and landscape. If your application only supports landscape or portrait
modes, just don't react to the inverted orientations.
Added orientation example screenorientation under examples/declarative.
The patch includes a fix for calculator example, which rotated to wrong direction when switching from portrait
to landscape. Also, improved qdeclarativeviewer unit tests. Changes have been tested to work on Windows,
Linux and Symbian^3.
|
|
|
|
| |
QTBUG-12590
|
|
|
|
|
|
|
|
| |
directly from the base state.
Make sure qmlExecuteDeferred is called on the state being extended.
Task-number: QTBUG-12559
|
|
|
|
|
|
|
|
|
|
| |
PathView handles its own mouse interaction, but lacked properties
similar to those in Flickable to determine when it is stationary.
This made it impossible to start an animation when the view stops moving,
for example.
Task-number: QTBUG-12497
Reviewed-by: Warwick Allison
|
| |
|
| |
|
|
|
|
|
| |
Task-number:
Reviewed-by: Michael Brasser
|
|
|
|
|
|
|
| |
having different contents
Task-number: QTBUG-12339
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
| |
Broke signal handlers in QML
Task-number: QTBUG-12335
Reviewed-by: Aaron Kennedy
|
|
|
|
|
|
|
|
| |
This allows dragging a MouseArea that contains a clickable MouseArea,
for example.
Task-number: QTBUG-12323
Reviewed-by: Michael Brasser
|
| |
|
|
|
|
|
|
|
|
| |
The boundingRect depended upon the image cache which may not become
valid until after boundingRect is called.
Task-number: QTBUG-12291
Reviewed-by: Michael Brasser
|
|
|
|
|
|
|
|
|
| |
The wantsFocus property has been renamed to activeFocus, to better
reflect its value. Reading and writing the focus property is also now
consistent -- this property represents focus within a scope. Other small
changes were made to keep things consistent with the new naming.
Reviewed-by: Aaron Kennedy
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise a Behavior may mistakenly not be triggered. This situation
can arise when the property in question has been manipulated via the
property system, followed by a direct function call (which correctly
bypasses the Behavior), followed by a another change via the property
system.
Task-number: QTBUG-12295
|
| |
| |
| |
| |
| |
| |
| | |
... and percentage is useless.
Task-number: QTBUG-12282
Reviewed-by: Warwick Allison
|
| |
| |
| |
| |
| |
| |
| | |
height explicit
Task-number: QTBUG-12273
Reviewed-by: Michael Brasser
|
|/
|
|
|
|
|
| |
i.e. the thread with the QNAM the original reply was created in.
Task-number: QTBUG-12302
Reviewed-by: Aaron Kennedy
|
|
|
|
|
|
|
| |
We need to create our cached image in boundingRect() if it doesn't
already exist, to prevents painting errors.
Reviewed-by: Warwick Allison
|
|
|
|
|
|
| |
Also parent them back to the VIM to ensure correct destruction.
Task-number: QTBUG-12261
|
|
|
|
|
|
|
| |
QDeclarativeVisualDataModel::stringValue() did not handle
QList<QObject*> model types.
Task-number: QTBUG-12005
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
The scale of the delegate was used to offset the item. This was a
bad way of making the item appear to be positioned correctly when
the default transform origin was the top-left. Now that transform origin
is center, it is obvious that it was a bad idea.
Task-number: QTBUG-12245
Reviewed-by: Michael Brasser
|
|\ |
|
| |
| |
| |
| | |
Task-number: QTBUG-10658
|
|/
|
|
| |
Task-number: QTBUG-12167
|
| |
|
|
|
|
|
|
|
|
| |
Ancestors of the item with focus should only report wantsFocus as true
when they are a FocusScope or a top-level item.
Reviewed-by: Aaron Kennedy
Reviewed-by: Yann Bodson
|
|
|
|
|
|
|
|
|
|
| |
in the Compiz window manager which leads to the QML viewer mainwindow not
being composited anymore (at least until the next resize).
Since we need to somehow switch between fixed size and freely resizable
views, we have to work around that bug using the layout constraint hints.
Task-number: QTBUG-11771
Reviewed-by: kkoehne
|
|
|
|
| |
(onvert to use SpringAnimation and SmoothedAnimation instead)
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-12086
Reviewed-by: Michael Brasser
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Replace the usages of Follows with Behaviors, update docs.
|
|
|
|
|
| |
(should be handled by image providers, elements shouldn't have to know
about the capabilities)
|
|
|
|
|
|
| |
QDeclarativeImageProvider to provide pixmaps instead.
Task-number: QTBUG-11980
|
|
|
|
|
|
|
|
|
|
| |
synchronous loading of QImages. (QPixmaps can only be created in the
main thread so they will always be loaded synchronously).
This changes request() to requestImage() and adds requestPixmap()
for pixmap support.
Task-number: QTBUG-11989
|
|
|
|
| |
QTBUG-11933
|
|
|
|
|
|
|
|
|
|
|
|
| |
This may mean that the cursor is to the right of the width, so components should
cater for that with a margin if they are boxed / clipped.
TextInput used to try to account for right bearing (and left bearing incorrectly since
it added it on the right). This is removed. Potentially this means that for some fonts
the text repaints incorrectly on the left or right, but if that is the case Text and TextEdit
already had such a problem (undetected), and all will need fixing.
Task-number: QTBUG-11983
|
| |
|