| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
two separate clicks
Task-number: QTBUG-14832
Reviewed-by: Martin Jones
|
|
|
|
| |
Task-number: QTBUG-14792
|
|\ |
|
| |
| |
| |
| | |
Task-number: QTBUG-14792
|
| |
| |
| |
| |
| |
| |
| |
| | |
New mode requires them to at least compile.
Now that I've noticed this, removing that check on compile failures in
QDeclarativeTester.
Task-number: QTBUG-14792
|
| |
| |
| |
| |
| |
| | |
This reverts commit 8ba02a8f5a537b9f7e1ff671abe6eed67029db58.
ExpectFail state has been altered. Redoing that commit.
This commit also adds the new line to indicate tests we don't care about
|
| |
| |
| |
| |
| |
| | |
Also remove the check for the old way in tst_qmlvisual
Task-number: QTBUG-14792
|
| |
| |
| |
| |
| |
| |
| | |
The bug found in gridview.qml doesn't actually stop the test from
passing, so it's now updated.
Task-number: QTBUG-14792
|
|/
|
|
|
| |
This reverts commit b6ee57e14e145d9caa3f572d55447ec92f78cea4.
Changed our mind about how to mark tests as expect-fail
|
|
|
|
|
|
|
|
|
|
| |
This property can be set with a reason to skip the test (i.e. known bug)
and the failure will not count for blocking purposes.
This change also alters one of the failing tests to use the new property
Task-number: QTBUG-14792
Reviewed-by: Michael Brasser
|
|
|
|
|
|
| |
Still looking into text/fonts/plaintext which just developed an issue.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Until this element is maintained, all tests are entering expectFail
state.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Replace text with coloured rectangles, for more cross platform stability
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Mostly just creating the test scripts.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Still correct, main problem was not getting updated visuals when
we switched away from follows.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Smoothed animation test is actually just a subset of smoothed follow now
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
dynamic.qml is now at expect-fail status, see QTBUG-14839
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
The only difference appears to be a change to the flicking parameters,
so the test is still valid.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
update visuals, and add a couple comments.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Includes the task numbers of the bugs, for later processing.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
They are mostly still fine, it's just that the flickable parameters
had changed. Expected outputs have been revised.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Includes speeding up the animated resize tests.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Apparently this is something we've had troubles with in the past
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Also fixes a doc typo. Includes test.
Task-number: QTBUG-14469
|
|
|
|
| |
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Shorten duration and remove the element of flicking (not under test).
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Platform visuals and some cleanup after extended neglect
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Platform visuals and working again after a long period of neglect
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Getting them running again, and smaller. Need to fix a bug before they
pass again though.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
Remove text, to make them less platform specific
Task-number: QTBUG-14792
|
|
|
|
|
|
|
|
|
| |
Add platform specific colorAnimation Visuals
remove color animation from propertyAction
remove gradient from qtbug10586
shrink scriptAction-visual.qml
Task-number: QTUBG-14792
|
|
|
|
|
|
| |
listview.qml is still expected to fail, filing a bug about that soon
Task-number: QTBUG-14792
|
|
|
|
|
| |
Task-number: QT-3957
reviewed-by: Aaron Kennedy
|
|
|
|
|
|
|
|
|
| |
The delayed removal items weren't handled correctly by
mapRangeFromModel() function. Use mapFromModel() instead which gives us
what we actually want and remove unused mapRangeFromModel().
Task-number: QTBUG-14471
Reviewed-by: Michael Brasser
|
|
|
|
|
| |
Authored-by: Roberto Raggi
Reviewed-by: Aaron Kennedy
|
|
|
|
|
|
| |
Follow-up to e11ee40cefc981fbdcfb10816039d4efb080fb17.
Reviewed-by: Yoann Lopes
|
| |
|
|
|
|
|
|
|
|
| |
Properties have always had precedence over methods in C++ classes, but
erroneously, not in types declared in QML. This was because the property
cache for the two went through a different code path. With changes
0c06e59577df1ec715e67d6d5842800bcec24945 and c407d79f79c67f2f2bb84efc93061fd57fe4cf54
the code paths were unified and this bug was exposed.
|
|
|
|
| |
Task-number: QTCREATORBUG-2769
|
| |
|
|
|
|
| |
Task-number: QTBUG-11604
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
Task-number: QTBUG-14449
|
|\ |
|
| |
| |
| |
| | |
Task-number: QT-4094
|
| |
| |
| |
| |
| |
| | |
in Text painting
Task-number: QTBUG-14374
|
|/
|
|
|
|
|
|
|
|
|
| |
The behaviour of setting the currentIndex out of bounds, was different
depending upon whether it was set -ve, beyond the end, or before
component completed. The behaviour is now consistent - setting the
currentIndex out of bounds is allowed and will cause the currentItem
and highlightItem to become null.
Task-number: QTBUG-12571
Reviewed-by: Michael Brasser
|
|
|
|
| |
Task-number: QT-4093
|