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>

Remove useless set of MOC_DIR, OBJECT_DIR,
RCC_DIR and UI_DIR.

Change-Id: Iba08d517e096a982f2bae9701083ebc40ee78ea2
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Positioning an item to a sub-pixel position might cause the item to
not appear as crisp as it should be.

To prevent this, the layout will round off the position and size to the
nearest integer.

Task-number: QTBUG-31038

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

Qt Quick Layouts is a module by itself and it is misleading to
list its items here.

Add a note instead to say that Qt Quick Controls can be used with
Qt Quick Layouts.

Change-Id: I0e0a506f5ff7f2702126388fa60ff075ee2cbb4e
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

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

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

It seems pure qml projects don't really work in our
examples architecture at the moment. This change
adds a simple main file and resource bundle to
each of the example folders.

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

This is not needed.

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

Change-Id: I7046e9aeab5efe8bd32fcfb0d1bf571892921e30
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

This reverts commit c5270bdb7261deaeed13c49ba8b4c17825b5619b

Since we reverted Change Ia638064f: Return infinity instead of -1 as a default value for max sizes, we have to revert this one as it depends on it.

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

This reverts commit a4158c97d84d5c76126307213baf22d12babdbc2

This commit breaks the basiclayouts example so I am reverting it until we have a revised ifx.

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

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

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

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

- New header graphics
- Lighter buttons
- Lighter and better scroll bars
- Fixed incorrect focus for tabs
- Removed borders on item view rows

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

With commit 16558ac7


Layout.maximumWidth and Layout.maximumHeight now returns
Number.POSITIVE_INFINITY instead of -1.
As described in that commit, comparisons against those properties
does not need any special handling for -1 anymore.

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

Having a screenshot will make the example appear in Creator Welcome
mode as well.

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

This was a bit inconsistent, because in the case of a Rectangle its
Layout.maximumWidth would return -1 by default (which was supposed to
be interpreted as infinity) However, since the maximumWidth propagated
up to the layout, the layout.Layout.maximumWidth would return
1000000000. Adding two Rectangles to the layout would make
layout.Layout.maximumWidth return 2000000000, and adding a third item
with Layout.maximumWidth:1 would make layout.Layout.maximumWidth
return 2000000001

With this change, since infinity + number = infinity, everything
that can grow to infinity will just return infinity.

In addition a developer can now more intuitively do comparisons
like this:

if (value > Layout.minimumWidth && value < Layout.maximumWidth)

instead of

if ((value == -1 || value > Layout.minimumWidth) &&
    (value != -1 && value < Layout.maximumWidth))

Now, as a bonus, it becomes less consistent to set an attached
(min,max) property to -1 in order to reset it to its implicit value.

This also fixes a documentation issue with regards to the attached
Layout.{min|max}imum{Width|Height} properties. It only told the story
correct if the item was not a layout, and updates the docs for the max
sizes to mention that it returns Number.POSITIVE_INFINITY

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

When a layout did not have an implicit size nor any of the
Layout.preferred* properties set, the size hint calculation would
fall back to retrieving the width and the height properties of the
item. It would then store that value in the Layout.preferred*
property. This was wrong.

This could be a problem when an item was later added to the layout,
and consequently the implicit size of the layout got updated.
However, since the layout now had a preferred size set, a parent
layout would ignore the implicit size it had since it would settle
with the Layout.preferred* property (that's the rules the
effectiveSizeHint_helper work with).

The fix is to set the implicit width/height instead of the
Layout.preferred{width|height} property.

The compare in the test was actually by accident wrong, which can be
easily verified.

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

..than the implicit size of the layout.

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

..to be smaller than the GroupBox' implicit size.

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

This reverts commit 390c6fa6

.

We actually do use this to set the background color.

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

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

The bug QTBUG_30379 has been fixed.

Change-Id: Ic05f70e3dec528cacefba44d14a76952b5636315
Reviewed-by: Liang Qi <liang.qi@digia.com>

Task-number: QTBUG-29893

Change-Id: I7c80a68d9d45c3df3e0bf691b69c4510ccd1649d
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

The mousearea in TableView has to accept mouse event in onPressed to
receive upcoming double click event.

Regression introduced by Iff3e5c1.

Instead of not accepting the event in onPressed, set the MouseArea
property propagateComposedEvents to true and does not accept the onClicked
event.

Also uses QStyle::SH_ItemView_ActivateItemOnSingleClick to check if the
table is activated on single or double-clicking. By default, it is activated
on double-clicking.

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

There are three ways to add tabs:
- declare 'static' Tab { } child elements
- call addTab() / insertTab()
- Component::createObject(tabView)

=> Do not rely on the calling order of Component.onCompleted()
and make sure that the same tabs are not accidentally re-inserted.

Task-number: QTBUG-30873
Change-Id: Ib30cfb676debbb302c5e9f7d757f66aab6fcc684
Reviewed-by: Caroline Chao <caroline.chao@digia.com>