| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Task-number: QTBUG-17280
Reviewed-by: Martin Jones
Change-Id: Ibbbd2da44d5826b6e499b731eda66b2016bade85
|
|
|
|
|
|
| |
Task-number: QTBUG-17280
Reviewed-by: Martin Jones
Change-Id: I34a623b49ce0fd5c05ae7a7ea5d0437c107b8a9b
|
|
|
|
|
|
|
|
| |
Overridden as readonly for elements that have an inherent implicit size
such as Text, TextEdit, TextInput, positioners, Loader.
Task-number: QTBUG-14957
Reviewed-by: Michael Brasser
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We would previously call subFocusItemChanged(0) on the item as part of
clearing the subfocus, even if the item in question would recieve a new
subfocus item as part of setting the new subfocus.
This resulted in the declarative item emitting activeFocusChanged(false)
and then activeFocusChanged(true), which was affecting any animation or
state bound to the activeFocus property of the item.
We now stop clearing the subfocus when encountering an item that we know
will get subfocus during the set-subfocus pass. We then set subfocus all
the way to the root item, since the subfocus item itself might change.
The effect of this is that the declarative item will only get one call
to subFocusItemChanged(), passing the new subfocus item, instead of two.
This means the declarative item can keep track of wherther ot not it had
a subfocus item previously, and only emit activeFocusChanged() when the
active focus goes from true to false or false to true.
Task-number: QTBUG-15615
Reviewed-by: Yoann Lopes <yoann.lopes@nokia.com>
|
|/
|
|
|
|
|
|
|
| |
When using KeyNavigation, if the "visible" or "enabled" property of
the item set in the KeyNavigation handler is false, an attempt will
be made to skip this item and setFocus to the following item.
Task-number: QTBUG-15862
Reviewed-by: Martin Jones
|
|
|
|
|
| |
Task-number: QTBUG-15694
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
|
| |
This patch makes the handling of properties like
children and data easier in Bauhaus.
Especially in the case of property alias
Reviewed-by: Aaron Kennedy
|
|
|
|
|
|
|
|
|
| |
Sharing a NOTIFY signal can cause binding loop warnings with no apparent
cause.
Task-number: QTBUG-12333
Reviewed-by: Aaron Kennedy
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
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
This also optimizes the implementation.
Task-number: QTBUG-11383
|
| |
|
|
|
|
|
|
| |
Allows intercepting keys before or after normal item key processing.
Task-number: QTBUG-10467
|
|
|
|
| |
Task-number: QT-714
|
| |
|
|
|
|
|
|
|
| |
QDeclarativeItem will be public, all properties that are relaying on
private types must be private too.
Reviewed-by:akennedy
|
|
|
|
|
| |
Task-number: QTBUG-9772
Reviewed-by: Alexis
|
|
|
|
|
|
|
|
|
|
|
| |
This commit add a extension object to bring the anchors property for
a QGraphicsWidget. The actual implement uses a separate object for storing
the anchor pointer. In the future it would be nice if the extension object
is the anchor itself. Also there are two connects extra for QGraphicsWidget
one can perhaps disappear with a later commit. Only baseline case is not
supported because QGraphicsWidget don't have any concept of baseline.
Reviewed-by:akennedy
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
src/declarative/graphicsitems/qdeclarativeitem.cpp
|
| | |
|
| |
| |
| |
| |
| | |
For properties that are as important as "parent", QML cannot afford the
overhead of a signal/slot connection.
|
|/
|
|
|
|
|
|
|
| |
This commit remove the children property from QDeclarativeItem because
it's now in QGraphicsObject. This commit also get rid of width and height
properties to use the one in QGraphicsObject.
Task-number:QT-2757
Reviewed-by:akennedy
|
| |
|
|
|
|
| |
should fix the current failure when building on windows.
|
|
|
|
|
| |
Task-number: QTBUG-7193
Reviewed-by: akennedy
|
|
|
|
| |
Task-number: QT-3046
|
|
|
|
|
|
|
|
|
|
| |
Private headers should include other private headers by:
#include <private/qfoo_p.h>
Using a relative path works during the build, but does not work when
building other projects which attempt to use the installed private
headers (e.g. unit tests for private classes).
|
|
QDeclarativeXXX.
|