Sometimes there is no trivial mapping between model and values.
Change-Id: I2617f14828b97ba7352aa3a8f3d2ebb9fd2f3809
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Commit any data to the backend if the selection will change.
The signal editingFinished is usually triggered to late.
Change-Id: Ib7adfd32a50ae94b017a7587e81721176440a988
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
This patch ensures that we only commit data to the backend
if the text actually changed. The signal onEditingFinished is triggered
even if the user did not edit the string.
Change-Id: I2d54f3d79a1c60525e4c9744b364cc014bd407ce
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
The small ColorCheckButton has to preview the same color as the rest
of the color editor. Before this patch it was showing the color
defined in the backend as rectangle color.
This is not correct in gradient editing mode.
Also the binding in Colorbutton was deleted assigning values
directly.
Task-number: QTCREATORBUG-12204
Change-Id: Iad5263ccccba10fdb4f2b757f6965d500c50ac53
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Instead we connect to the selectionChanged signal and do the setup there.
Change-Id: Ia44887fa794c9726b3c4111e1b1f37ba2baaafc5
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Both forms are functionally equivalent, but the official documentation
favors the shorter one.
Change-Id: I2b6fccfafc2474f5b61ed6dce460b0472a63854c
Reviewed-by: Jarek Kobus <jaroslaw.kobus@digia.com>
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
We have to properly setup the color of the color editor, if we add or
remove a gradient.
Change-Id: I3aac64e9957036343ff304f1b163c4c480b5e976
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
On some systems the fonts are eally huge, so we have
to allow much more space for the leading label.
Task-number: QTCREATORBUG-12106
Change-Id: I7ad6687c4af15b2126efe2c3bd8284d36d9ac633
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
We react to selection change now and keep the selection.
Change-Id: I847b8cf308277df92295822f9cd18ebb58cc2ba0
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
We have to wait until the model is properly set until we react
to currentTextChanged. We also have to guard against binding loops.
Task-number: QTCREATORBUG-12257
Change-Id: Id602f6f192962e83a6166bf24a0711b22baa7868
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
Using hasToConvertColor to handle the alpha channel.
Change-Id: I6b6e2ef4361efb7aba3adaf549cbddd625145e33
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
For color properties we have to take care of the alpha channel
manually.
Change-Id: I2cbb5a2c45a16385068e771e1a1ca8a10f47a7bf
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
There are two values now, one to limit an entry in the L&E view
(default 100) and a hard upper limit (at 1 mio).
If displayed values are elided, the true length is shown in addition.
Change-Id: I180b70446c18e258c164e5af75b88d4c8b6c53f2
Reviewed-by: hjk <hjk121@nokiamail.com>
Checking for visibilty is a bad idea. Instead we check if
the item actually has a gradient.
Change-Id: Ib14de1fbc570c28332e7e240052b4820c5b1483c
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Also add '...' for cut-off std::strings.
Change-Id: Ib6129eb43c723f2a863086a0142312c669b65665
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
The range boundary and stride can be integral expressions.
Also ( ) are valid delimiters now, making descriptions like
list.at(2.(4).100+2) acceptable.
Change-Id: Ief68c0a1b0b0d3813b2939d60e0806f5cd3ff0b0
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Multiple expressions can be separated by semicolon,
and arrays allow index ranges given as [a..b] or
with strides [a.(s).b].
Change-Id: I0b7b4ee500a5f6f5027d777b0a1e8ee5a28a7cd5
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
The ColorButton did change the color as a side effects of rounding error.
With this patch the ColorButton does onyly change the color as a result
of user interaction.
Task-number: QTCREATORBUG-12202
Change-Id: I6504713a27fe7b562b8342229bd287af23156602
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
The old property editor did support tooltips and many labels
have properly defiend tooltips.
In QtQuick.Controls we have to use private API for tooltips
to show up.
Change-Id: If1c50b58e8388b8846c2dd07fcd326f09d67d127
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
We need to set the text to the value, so that the user can see which
value is explicitly set.
Task-number: QTCREATORBUG-12195
Change-Id: I0b405839122f3b008790df3e3c2b0b7728299b7a
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
