If the lightness or saturation are 0 then hue is undefined.
If lightness is 0 then saturation is undefined/0.
Nevertheless we should keep the old values in the ui, because
the user should not loose the values in case he increases lightness
or saturation later.
Change-Id: I9fd80f6ca84fa08ef62d9fbb6dd4afce992c3546
Reviewed-by: Tim Jenssen <tim.jenssen@theqtcompany.com>
The rendered text is still ugly, but the fuzzy text is better than the
alternative currently.
Change-Id: Id9e54fb406ee964e0b9b5c40b7a8108b45c15f85
Task-number: QTBUG-42861
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
Use the background color property in the QML code instead of relying on
QQuickView::setColor
Change-Id: I556515a42d9483f88500fa5a5c56ea21f48fa685
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Use register names as handle, not their index in the view.
Store the raw real values, not some stringified version
as primary data. Use subentries to break down bigger
registers into smaller entities. Also remember the
previous value of a register and show it in a tooltip.
Change-Id: I8ae3cc8766a7b211bc7cc827c734e5cf6060825c
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
Has not been usable for a while and will be superseded by
"native" mixed stepping.
Change-Id: I2902a98b7ad4e4b29e389e54fb6488bf711840dd
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
It's confusing in the presence of the global function of that name,
and it's better to distinguish type names and type objects anyway.
Change-Id: I3e0674dbc96a8e2b245ed61fabd2fe7cac5a72e5
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
We will need access to more dumper data later.
Change-Id: Id8fe09b192ac7d2ae822a0323cda13c0e2ff81e3
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This will be useful to create artificial QML stack frames.
Change-Id: I41cb87f8dea69d88695fea46a1ae2b0270cbec1a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
The underlying problem here is still that we can deduce
the item type from the map type except by string manipulation
and type lookup. Which fails at times.
Change-Id: Ibe6a8ca1fbd84c43c7d31b65e017792d1b6a1e0b
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
There is seemingly still no proper API for that, and
the old hack broke. Use a new one.
Change-Id: I9e638ca1fbd84c43c7d31b65e017792d1b6a1e0b
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
Do not use the hardcoded value in the xml highlighter file.
Task-number: QTCREATORBUG-13538
Change-Id: Ie79f46e2ab31caf01c0ab58097756141691761f0
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
It is very often a mistake to define a destructor without a copy (and move)
constructor and assignment operator. In C++11 no move constructor and
assignment operator will be generated if a destructor is defined. So it is
better to omit a lonely destructor in out template.
https://en.wikipedia.org/wiki/Rule_of_three_%28C%2B%2B_programming%29
Change-Id: If911556f872d878939f0f2fcaa974494a4df8a8a
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
The old code worked around some issue that is not present
anymore and breaks now by itself. So remove the workaround.
Change-Id: I41a017ced91198bdc4e822cfcc1c45580945a773
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
Export the form contents as a list of lines and join them when
needed instead of hoping to unescape '\\n' in all places where
it is necessary.
This approach should be a bit saver since it will cause parse
errors in the wizard, which are more visible than broken output
in the generated files.
Task-number: QTCREATORBUG-13456
Change-Id: I434a9227082f92be3c2ce75006f61ac79a2b6fd6
Reviewed-by: Daniel Teske <daniel.teske@theqtcompany.com>
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
The fixup expando will be applied before validating a string in a
lineedit. It uses the special "%{INPUT}" variable for its input and
any change will be applied to the LineEdit.
Change-Id: Ia496eacdbe541d418acb4a977c274527387896ca
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This avoids sub pixel antialias artefacts.
We call disableNativeTextRendering() in updateDirtyNodesRecursive(), because
items might be created or change the property after component complete.
Change-Id: Icd9c87b69434a910c9555540ba7bafdc874afc5a
Reviewed-by: Tim Jenssen <tim.jenssen@theqtcompany.com>
There were a couple of situation where the is_optimized_out flag
was not used and later produced (caught) exceptions on access,
or where the still availably type was not shown.
Change-Id: I7ad5aa09a19357e50739d9fdf32f7423e30fe011
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
Label respects the system palette, while Text does not.
Task-number: QTCREATORBUG-13189
Change-Id: Ife1796cd04216eef909820f85dfdfd9c403ae80f
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@theqtcompany.com>
This can cause "TypeError: 'float' object cannot be interpreted as
an integer" otherwise.
Change-Id: Icae026f8f47edb686e22ce417f3bbdf41bbf0bc1
Reviewed-by: hjk <hjk121@nokiamail.com>
Previously, hovering over 'i' when stopped in main()
int foo() { int i; }
int main() {}
produced a tooltip without contents, now there is an
item saying "<not accessible>"
Change-Id: Id4de72541f74af93ba65c2a9508cf21e1dcd6569
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
The size of the project list should only depend on the size of the items,
not on the size of the parent.
Task-number: QTCREATORBUG-13387
Change-Id: Iad8a32999a277532c2b64a7a889ddaafa40f693b
Reviewed-by: Robert Loehning <robert.loehning@theqtcompany.com>
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
This change adds an additional color role for the border color of a
pressed button.
Task-number: QTCREATORBUG-13356
Change-Id: Ibdbd330f60063961dbf27dbe2fb90f32089d7b34
Reviewed-by: Thorben Kroeger <thorbenkroeger@gmail.com>
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
Use same role for info bar and search result widget
Change-Id: Ibe1f226d4ea8edaafb3daa1cc629e23a48322cf2
Reviewed-by: Thorben Kroeger <thorbenkroeger@gmail.com>
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
