| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
(cherry picked from commit e46c44f9538dbe5b44ce61d3a42403cfa471ae8b)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Was causing assert failure on windows if the 'c:' was lower case,
since it was being added to the import path database with a lower
case and thus later lookups with an upper case 'c:' would fail.
This change fixes the check for whether the path refers to a
local path or not.
Task-number: QTBUG-16885
Change-Id: I0a2a2f705443ed453fb2b13f8599e035c2bd2877
Reviewed-by: Martin Jones
(cherry picked from commit 33512bc223be373975426ffcc6f8fa783a7582c9)
|
|
|
|
|
|
|
|
| |
Added tests for remote imports and fixed/improved examples and
text in the docs.
Change-Id: I8f411a0287c4d50ec3cebe5567d803689cd5b1c7
(cherry picked from commit d7e42d7c5b0eb6513526d0c21025939a467e8d68)
|
|
|
|
|
|
|
|
| |
(cherry picked from commit a78f6b1718b8285cb65ae989a070bf8703746b5d)
Conflicts:
tests/auto/declarative/qdeclarativemoduleplugin/qdeclarativemoduleplugin.pro
|
|
|
|
|
|
|
|
|
|
|
| |
Some refectoring while fixing QTBUG-13687 resulted in the private
setOffset() method being called rather than the public. The
public version was responsible for updating currentIndex.
Change-Id: Iac9c7a19d6fa64550b9498e77b8983512e199370
Task-number: QTBUG-17319
Reviewed-by: Michael Brasser
(cherry picked from commit eb1db74fb59ecb40d541644ce31ce7ec7b2620d2)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QML supports versioned types in modules. There's a version major and a
version minor.
This makes it possible to have a module com.organisation.fancycomponents
with version 1.0, and later you could ship a new module
com.organisation.fancycomponents which contains a more recent version 1.1
or 2.0 AND also the old versions to keep old code running.
This is good.
The problem is that this is difficult with certain QA procedures. It's
hard to verify that a new module is indeed 100% compatible with the
previous versions.
The change extends the import mechanism by adding optional versioning to
the component patch.
With the patch, you can add a new module
com.organisation.fancycomponents.2.0 which will be loaded when the
QML file specifies "import com.organisation.fancycomponents 2.0".
The patch works as follows: if you try to load
com.organisation.fancycomponents in version 2.0, the engine first
looks for com/organisation/fancycomponents.2.0, then for
com/organisation/fancycomponents.2 then for
com.organisation/fancycomponents.
Reviewed-by: Aaron Kennedy
Task-number: QTBUG-16455
(cherry picked from commit dd49b322b327fe87d8420abcce0e6cee877a88d7)
|
|
|
|
|
|
|
|
|
|
| |
We positioned the view beyond the bounds, which in some cases resulted
in only one item being created. Combined with a bug in the bounds
fixup very many items were created.
Task-number: QT-4441
Reviewed-by: Michael Brasser
(cherry picked from commit c3dd455b03a6c03011e2446f69fc262230e91639)
|
|
|
|
|
|
| |
Task-number: QTBUG-16769
Reviewed-by: Bea Lam
(cherry picked from commit 7ddec9f3179bfd854ae53e23ab292de1f9a26377)
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 82ff3f484c7ec49e60b7fddf23794937974a6768.
QTBUG-16796 reports that this commit is causing regressions
relating to initial sizing of items.
Task-number: QTBUG-16796
(cherry picked from commit 8c3086aa36b51a9731fce8eb8146b33ab8196aed)
|
|
|
|
|
| |
Reviewed-by: Trust Me
(cherry picked from commit ac5c099cc3c5b8c7eec7a49fdeb8a21037230350)
|
|
|
|
|
|
|
| |
This updates the tests to match the correct behaviour as of
1ba3e41f09ea719249286fede5d3fe96621ccb61
Task-number: QTBUG-16357
|
|
|
|
|
| |
Task-number: QTBUG-16319
Reviewed-by: Martin Jones
|
|
|
|
|
| |
Task-number: QTBUG-16356
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
|
|
| |
If the model is a VisualDataModel, the count will initally be zero
and modelCount is not updated due to itemsInserted() before the
component is completed.
Task-number: QTBUG-16357
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
| |
selftest_noimages and qdeclarativespringanimation were correct, updating
test scripts to match.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Minor changes in flickable and rectangle radius behaviours have led to
some altered pixels here and there.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
|
| |
Call canFetchMore()/fetchMore() on setModel(), setRootIndex() and when
the last item is created.
Task-number: QTBUG-16039
Reviewed-by: Bea Lam
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-16133
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
|
| |
The grab was not always kept by filtering Flickables, but would remain
set next flick, resulting in toggling of flicking.
Task-number: QTBUG-16177
Reviewed-by: Michael Brasser
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When delayRemove is true and all visible items are tagged to be
removed the visibleIndex became invalid and refill() began filling
from 0.
Task-number: QTBUG-16183
Reviewed-by: Michael Brasser
|
|
|
|
|
| |
Task-number: QTBUG-15836
Reviewed-by: Michael Brasser
|
| |
|
| |
|
|
|
|
|
|
|
| |
Check bounds in TextInput and TextEdit.
Task-number: QTBUG-16188
Reviewed-by: Bea Lam
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
|
| |
Url fragments and queries were being removed from the image ids
passed to QDeclarativeImageProvider.
Task-number: QTBUG-16195
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
| |
Current state reset mechanism does not really work for Text elements as the keeping implicit correct would require relayouting of text twice (See bug QTBUG-15118). Changed QDeclarativeState reset autotest to use Image element instead of Text element until the issue has been fixed.
Task-number:
Reviewed-by: Yann Bodson
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
|
|
|
|
| |
Reverted a commit 2eee49127b80b5b56c605f76ccea004b03d89577 "Remove active selection when TextEdit loses focus". Contrary to TextInput, by default TextEdit keeps the selection visible when the editor loses active focus. If this is not wanted, a property called persistentSelection can be set false to make selection dependant on the focus.
|
|
|
|
|
| |
Task-number: QTBUG-15341
Reviewed-by: Yann Bodson
|
|
|
|
|
|
|
|
|
| |
If the view height is 0 no items will be created so the contentHeight
can not be estimated. The currentItem is usually created,
so it is possible to use that to estimate.
Task-number: QTBUG-16037
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
|
| |
Removing the currentIndex could result in currentIndex being > than
the number of items in the model.
Task-number: QTBUG-15926
Reviewed-by: Michael Brasser
|
|\
| |
| |
| |
| | |
Conflicts:
src/s60installs/eabi/QtGuiu.def
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
In some cases ListView and GridView would position the highlight
despite highlightFollowsCurrentItem: false being specified.
Task-number: QTBUG-15972
Reviewed-by: Michael Brasser
|
|/
|
|
|
|
|
|
| |
The calculation of position of currentItem when it is out of the
visible area was bogus.
Task-number: QTBUG-15525
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
| |
Changing the minimum size of the viewer changes the size of some of the
visual test outputs which were really small.
Task-number: QTBUG-14792
|
|
|
|
|
|
| |
It appears to lead to sporadic crashes in the CI system.
Task-number: QTBUG-14792
|
|
|
|
|
|
|
| |
Reintroducing text tests to X11, and updating a few tests where the
behaviour of the items has subtly changed (and it was deemed acceptable)
Task-number: QTBUG-14792
|
|\
| |
| |
| |
| |
| |
| | |
4.7-integration
* '4.7' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
fix line endings
|
| | |
|
|/
|
|
|
|
|
|
|
| |
If the header size was not set explicitly, but determined implicitly
from Text height, the view was not positioned so that the header
was visible when first shown.
Task-number: QTBUG-15599
Reviewed-by: Bea Lam
|
|
|
|
|
|
|
|
|
| |
When snapping is enabled the header was ignored and content would be
aligned with the first item rather than the header, when at the top of
the view.
Task-number: QTBUG-15710
Reviewed-by: Bea Lam
|
|
|
|
| |
Task-number: QTBUG-15697
|
|
|
|
| |
Task-number: QTBUG-15695
|
|
|
|
|
| |
Task-number: QTBUG-15720
Reviewed-by: Martin Jones
|