| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
..to Layout.fill{Width,Height}
This property now takes a bool, which enables you to write
Layout.fillWidth: true
instead of
Layout.horizontalSizePolicy: Layout.Expanding
Change-Id: Icf2e0dc4757938489908b8997d6c4e80c8be1c50
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
|
|
| |
This will be set to 'true' when any of the splitter handles are
being dragged
Change-Id: I715f8107ff1844b97df27d649f2d48785476adf9
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
| |
Change-Id: If9df032c76e36f385aacd30cc31d6f02574c6f11
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
|
| |
|
|
|
|
|
|
| |
Those connections are sometimes called after the SplitView has
been destructed and it causes warnings (i.e. tst_splitview autotests).
Change-Id: I42ae333e72c01edba78f69bb1e9de8b4f85dea2c
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
| |
|
|
|
|
|
|
|
|
| |
Found this bug while replicating the Creator layout.
Aparently the content item is the parent of children so it should
fill the contents of the SplitView, otherwise it will report a
width and height of 0.
Change-Id: I47a8e6cbecf8642e2d133a0be0dce0305a167c0c
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
|
| |
|
|
|
| |
Change-Id: Ifa95b8db73b78c3b46d7d18bc55aa06d2569c89e
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
|
|
| |
It now uses the gridlayoutengine from graphicsview, which
also gives us a well tested grid layout engine almost for
free.
Change-Id: I939ae4d2b321c8079935ff3374e8e5d10d02384b
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
|
|
|
| |
If the SplitView was initially hidden, and told to
show later, the handles ended up at wrong positions.
This patch will fix this.
Change-Id: Ia21fa1efcf30c36bf18e0d4f3ab0813c6b79afcc
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Also removes the RangeTab from the Gallery example, since its controls
use containsMouse and are no longer different from the same set of
sliders on the control tab. Adding MouseAreas to each control in
RangeTab to achieve the same animation would clutter the example with
boilerplate code.
Change-Id: I80d6f3bbf1b73229f4d0ae99dd2a65bc083e7099
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
|
| |
Most of the documentation was there already, just not using proper qdoc format.
Change-Id: Ia28a0da3b20151202cafdbc1b535a1921a48b1a6
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
|
|
|
Change-Id: I1db05195ada0b798a632da04fb256f030c894560
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
