In Windows XP style, we actually use different values
based on tab position. That means we have to pass these
values through the tab style option.

Change-Id: I65904a9a57326003cfddef1a12ada5dda2fa2eab
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

We want padding to be a grouped property as the
existing Margins property looks rather odd and
insconsistent.

Change-Id: I9e614f9161aaf01af200b19a1fb46a51beec6fb4
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Change-Id: I9f1690524e29cd7fe0ab35be216aca9a6edd35ca
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This makes it possible for the style to simply increment
or decrement the current index (consider arrow buttons).

Change-Id: I048924d7f1f506ecc3005d2ebdfeb01d5ea6ca40
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Let the style decide whether tabs should be squeezed or not.

Change-Id: I25bdd9a4d045583613e14b4cba680642eda2ab59
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: I86102ddb14371498b9451f247f1f709633e82458
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Now one can choose which set of styles should be used by the controls.
The value should be the name of the QtQuick/Controls/Styles subdir
(eg. QT_QUICK_CONTROLS_STYLE=Desktop).

NOTE: The environment variable is for internal use and may be removed
in the future.

Change-Id: I23919270cd1e2406534fafe1134739d145a93538
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

Change-Id: I3d5a4fe8ce277e92d28e0ff68c1dab0ad029ea4c
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Task-number: QTBUG-31135

Change-Id: I0d9b0a3cf9d1036e6940e10944c711cdd23d858a
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Empty corner items may be used as padding, so TabViewStyle::left/rightCorner
effectively replaces TabViewStyle::left/rightPadding.

Change-Id: I01f3a1552c3395352e8953456d3956f4f8c29aed
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Since scrollbars affect the document/viewport size and vice versa, we
must allow the layout loop to recurse twice until the sizes stabilize.
Furthermore, avoid nasty content size binding loops (from ScrollView)
by providing a specialized Flickable item that TextArea has full
control over.

Task-number: QTBUG-30832
Change-Id: I74fe6c5017e75aa411fdbb64087afa18e1221ce9
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: I1a247656b957c87ef728fb42b2b212e02b5e5cd9
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: I11096da2efdebf2a3a2e003c90e48e120f8ba5fd
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

- Removed contentWidth and contentHeight since it is not needed
- Exposed contentItem so that it can be designable.
- Respect the implicit width or height of the contentItem if it is the
only item of the GroupBox. Otherwise childrenRect is used.
- Modified the style so that the style takes care of only the
padding size and not the entire size of the group box.
- Fixed flat and checkable appearance for custom style

Change-Id: I2c7ec4cb7d5e6f96863847e8d8d6d6f52428364e
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Casting a QLayoutPolicy::Fixed to bool was fine since that would return
false.
However, casting a QLayoutPolicy::Shrink to bool would return true,
which would give wrong results. (The conditions only want to check if
the item can grow).

There were no bugs because of this, simply because the Qt Quick Layouts
API does not allow setting *only* the shrink flag.
However, it would become a bug if we ever added such a feature.

Change-Id: I781aec85117f45e12e49ba27f7ed8f5724f71bd9
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>

If no stretch factors were specified, we used the preferred size as a
stretch factor. Obviously, that didn't work if the preferred size was
actually 0.

This patch works around this by actually setting the stretch factor to
1.0 if this is the case.
This should work fine in most cases, except for the case where there
are also other items with a preferred size close to 0.
In this case, the item with preferred size 0 will just grow
faster than an item with e.g. preferred size 0.1.

Task-number: QTBUG-31217

Change-Id: Id5a3e19c9cd756860fc4052daee3eb5582f39d0c
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>

Add autotests.

Task-number: QTBUG-31033
Task-number: QTBUG-30971

Change-Id: If82d5a9b6200e62d358ffc83e55137bab9b242c5
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

When nextItemInFocusChain is out of the TabView, the tabitem in TabBar
will get focused.

Autotest is included.

Change-Id: If5701afa1aeed16383b8d96483342a4629293997
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

We changed the TabView api from int to string so now we need
to translate to the style.

Change-Id: I9dafd9166a552a38eec06f46f4c6d4697b10eff6
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Change-Id: I5386e2b4af37c1dbad50740c748e953c81c85d22
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

We have to maintain the handle offset until the drag operation
has ended. If the user clicks outside the handle, we center
on the cursor position as before.

Task-number: QTBUG-31042
Change-Id: I8f23d998774278c6353d31b6fffea54596f7158e
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Change-Id: Ie47788f95d2ebfb0143bbccc77aa37efe155958d
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

The initialization of ignoreItem was simply wrong.

Task-number: QTBUG-31128
Change-Id: I67b41bc30099222d64aa6efb3c28e87a0ce043ca
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>

- Fixed missing press appearance of slider handle
- Removed drag threshold when pulling handle
- Ensure handle stays connected to mouse cursor by giving the fake handle size

Task-number: QTBUG-31042

Change-Id: I289a48b5fa67dde2792590645b8630a7ae6518d9
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Change-Id: I1ee810dfcd57fd9ff7ddf65c87208c8b457f755e
Reviewed-by: Nico Vertriest <nico.vertriest@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

Task-number: QTBUG-31160

Change-Id: Ife5837645636be1b2b2ee5cf9b0aa27ac04c2dc0
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Change-Id: I87a6a582824363197f66f6b7f6f29aa603123458
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

To avoid accidentally instantiating all rows at construction time, make
sure the rows have a valid (but arbitrary) height meanwhile the row
delegates haven't yet been loaded.

Change-Id: I1afc6bfa920886260717b3cb172fa0d858c0a8d5
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Task-number: QTBUG-31160

Change-Id: I7dc6e0d755093786e079f526e5ff5f6cbcfa94e0
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Just aligning our delegate api with the rest.

Change-Id: Ia8dc3c6dbf87431ff850a3e91f28c129072e2ee3
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Again trying to make the api a bit more consistent at using
row vs. index.

Change-Id: I769ca34c7bde628757a19fd47744b5cb1054a154
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

We are removing all references to index in the api
and sortColumnIndex should be renamed as well.

Change-Id: Ia8f0758e3ee4df161488aefff52bdb7b518a1f50
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

I was really confused because after assigning a model it looked like
the table view was showing the data, while in reality it was
just filling up with alternating row colors. I think it is
better not to draw anything to ensure that people correctly add
a TableViewColumn.

Change-Id: I353b478f4af80410aca3f94439a02ed7ab53f6d6
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

- Adds Menus to the front page so that we
can actually find essential types like Menu and Action.
- Added a basic example for Action
- I also added ExclusiveGroup to the Controls
category to make it accessible.

Change-Id: Ife980b786870d2bf07d709e024cb97396870e6c7
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

This reverts commit a454ff7f.

This patch should follow patch 91fc9b18



Change-Id: I5e26da1d967f8880d73e32ad5a76c59bedf7a065
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

They are strictly not needed...
As a consequence of this, do not limit the size of the TextArea

Change-Id: I3c152e7e8f749d7b5b2a0b9887664a11fb7d3b04
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This reverts commit 91fc9b18

.

This patch got reverted because it broke the basiclayouts example on Mac OS.

However, the bug was in the basiclayouts example, so we can still add
this patch.

Change-Id: I97c3cf30dd5a5c97916b4811d8be0b5b5a7ebb4e
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This broke with commit 24bbdab9



Task-number: QTBUG-31175

Change-Id: I684e9b09c4cdd39492b4859b5f46dacbca72bae5
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>

Because we use TableView as ListView, then only SpinBox, TextField, TextAre
and TableView could be selected.

Change-Id: I65ca106e60a57d86e029647653ae110fd81edaa4
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

task-number: QTBUG-31121

We already handle MouseWheel events separately and we do
generally not want to interact with the flickable.
I don't know if we should somehow handle this differently on a
mobile device but for now it seems sensible to disable it.

Change-Id: I7dc30050efcedd8f670b3ecdc0a9915a692fd475
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>