This might cause problems on certain platforms. While hard
to reproduce it seems safer to add the check.

Note that we do not get the alternating pattern if there is nothing
set on the model, but this was already the case.

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

Added more information for "Getting Started"
- Cleaned up some language
- Remove desktop specific
- Mention widget dependency
- Use QmlApplicationEngine in example

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

Also adding a new test for stepSize

Task-number: QTBUG-31441

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

Change-Id: I7da8e3664d6bd3ee9a8c4f22d4a5b686d1c5b5a9
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Do not bound explicit preferred size with implicit sizes. This
means that if Layout.preferredWidth was *explicitly* set to 50,
and Layout.maximumWidth had the implicit value 20, the effective
maximum width would be expanded to 50 in order to not disregard
the explicitly set preferred width. (covered by the tag
"expandMaxToExplicitPref" in test_sizeHint)

Note that this doesn't break any autotests, but the row layout
autotest was slightly changed to be able to add the new test cases.

This should make the behavior match the behavior of
QGraphicsGridLayout and QGraphicsLinearLayout

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

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

Those properties are, text, tooltip, iconName, and iconSource.

Also, properly capitalized gallery's tooltips.

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

We should set this to some decent default value that doesn't
look wrong. Note that the width and height definition in
TextArea could cause conflicts when used in layouts.

Change-Id: I815ff96c02f9a9a76c07d57181f3a24291c83c52
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

We only cared about reserving space for the height but while
trying to actually get the minimumSize for a window based on
the toolbar content I realized that we really need to calculate
the width as well.

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

Fixes issues including:
- Misspelled links
- Links to signal with arguments
- \table in SplitView.qml
- Links to current file

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

And:
- Add an index page for the Styles
- Add missing documentation for some properties (Component)
- Fix unexpected curly brackets in a couple of code snippets

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

This extra padding at the bottom is not needed and only serves to
make the borders uneven on mac.

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

This fix ensures that we can only add a TableViewColumn exactly
once. It also automatically expands the column with to the viewport
when only one column is in use.

In addition I have disabled dragging when columnCount == 1
as it was pointless.

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

Depends on https://codereview.qt-project.org/57500



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

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

We want to use more layouts in our examples as it is the
recommended way to create tool bars etc.

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

Using the implicitHeight of an item makes ToolBar and StatusBar
a lot more useable with layouts. In addition we enable the padding
property from the style, allowing its content to be positioned
in a more convenient way. This is similar to how we already do it
for GroupBox.

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

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

* List all applicable attached properties for each layout
* Move the stuff that describes min,pref and max sizes from GridLayout
  to the Layout docs.
* Document that all layouts \inherits Item. (Even if they don't directly
  inherit, this is consistent with how the positioners are documented)
* Add some links to Row, Column and Grid where appropriate
* Use \qmlattachedproperty instead of \qmlproperty for the attached
  properties. (Again, consistent with how the Positioners attached
  properties are documented)
* Change POSITIVE_INFINITE to the correct POSITIVE_INFINITY

Change-Id: Ia9272faa479b48a97300b031402c0380ca113d7b
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

And use \qmlattachedproperty instead of \qmlproperty for
properties in the Stack.

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

onItemVisibleChanged() was in some cases called after the dtor of
QQuickGridLayoutBase was called.

After having called the dtor of QQuickGridLayoutBase it would
continue to call the dtors of its base classes until it entered the
dtor of QQuickItem.  In QQuickItem it would call setParentItem(0) on
all its child items. This caused the item to become visible again,
thus it would emit visibleChanged() and finally invoke
QQuickGridLayoutBase::onItemVisibleChanged() which lead to the crash
(while trying to call the virtual invalidate())

The fix is to do an early return if we know that the layout is
in the destruction phase.
isReady() will return only true *after* the component is completed,
and before the component is destructing.

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

Change-Id: I59a9846c83340d0752659ef22cbb19a4be6a4129
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

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

The styleHints are not really flexible enough as a stringlist
as we want to be able to pass actual properties. Since we already
have a properties member of the style we should move all of our
internal properties to that.

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

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

Make Style inherit AbstractStyle, so it becomes the base class
of all styles. AbstractStyle also now has a default "data"
property so it's possible to conveniently declare helper
content inside styles.

Change-Id: Id84f3762cfae506e65021322619d7fb77b137994
Reviewed-by: Tomasz Olszak <olszak.tomasz@gmail.com>
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

The fooAt() type methods are reserved for coordinate based queries.

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

This adds some pixel tweaks on mac, adds minimum
size to fit the label and fixes dpi scaling on Windows

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

Otherwise, we won't be setting the shortcut on the platform item.

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

This property was not respected by some of the native styles
and makes more sense as a styling attribute.

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

Change-Id: I6f34ace6a24ce918cdd417bbfcd2fe8126aa321b
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

This change fixes the following things in .qdocconf:
 - CamelCase for project name
 - Proper selector for QML Types topic
 - Remove exampledirs since there is currently no example

(Both exampledirs and exampleinstallpath should be used
if examples are added)

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

Replace "property list<TableViewColumn> columns" with:
- addColumn(column)
- insertColumn(index, column)
- moveColumn(from, to)
- removeColumn(index)
- getColumn(index)

Exposing list<TableViewColumn> type of property in the public API was
problematic for several reasons. First of all, it limited the internal
implementation too much. Secondly, modifying the list programmatically
did not work as expected, and it also threw nasty warnings while
reordering the columns interactively.

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

We were still using "containsMouse" in a few places, and
we should consistently add "hovered" to all button types
for consistency. Also fixed the SplitView to follow the
new style conventions.

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

This ensures that double click to adjust content size on
headers doesn't end up eliding text. We also added
significantly more space by default.

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

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

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

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

It is about default behavior for QQuickWindow, when there is no any
activeFocusItem in the whole window, Tab/BackTab key could help you
to focus the item in the tab focus chain.

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

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