This also removes the display type selection, which didn't work
anyway. __m128 were only displayed as floats.
Change-Id: I2e3df0cd87a21abb0e3d844384e18cb9e5e6a021
Reviewed-by: hjk <hjk121@nokiamail.com>
I can't make it display the unsigned char[16] as a string and I have
no clue why. This is all magic to me...
This is good enough anyway
Change-Id: I1d78c01b3baaec8e7d4506552d79a536b573e9a6
Reviewed-by: hjk <hjk121@nokiamail.com>
linguist is not able to work with correct non-breaking spaces (cf.
QTBUG-6300 and QTBUG-35652), so we'll have to do entirely without them
for the time being.
Change-Id: Icd36556e141125335899e458102ade5728c6fbaf
Reviewed-by: Guillaume Belz <guillaume.belz@gmail.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
This is a somewhat different solution for improving the
performance of the welcome screen. It has the added benefit
of caching loaded items while still retaining a decent
performance.
Change-Id: I9927a90f1b7de5bb06c43b16dc80cb2afec3f8ad
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
It was only showing the "last" one because the inames were the same
(currentIName.None).
Do not overwrite iname of sub item in 'enterSubItem' if it already was
set.
Task-number: QTCREATORBUG-11109
Change-Id: I74581f62d47ff0c33650769c3ed66e24124d1092
Reviewed-by: hjk <hjk121@nokiamail.com>
That's what you get for shadowing a variable... The "childItem" variable
on the second part of the foreach refers to one declared on the first
part, which is uninitialized.
Found by ICC 14.0:
graphicalnodeinstance.cpp(300): warning #592: variable "childItem" is used before its value is set
Change-Id: I9079a428eda90f4bb06f9ccd1adf836fee119133
Reviewed-by: Kurt Pattyn <pattyn.kurt@gmail.com>
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
The designer was crashing when trying to anchor the root item.
The root item cannot be anchored.
Task-number: QTCREATORBUG-11078
Change-Id: I1aec1ad5b15de8c2baf3b76358d02347fb3a124c
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
The handling of expressions in states was broken in conjunction with states.
This patch fixes a couple of related issues:
* The notifier of isTranslated (PropertyEditorValue) has to be
expressionChanged, since this property depends on the expression.
* isTranslated() has to return also true if there is only an expression
in the base state. If the string is translated in the base state it
should be translated in other states, too.
* In states the expression set in createPropertyEditorValue() has to be the
expression of the current stateif there is one.
We can not just fall back to instanceValue.
* I did a couple of fixes in LineEdit.qml. We cannot bind checked directly,
since the binding will be deleted when checked is changed by the control.
I removed all code regarding transactions. We react to onEditingFinished,
so it is not required. The translated state is properly preserved now, when
setting the value.
Task-number: QTCREATORBUG-10674
Task-number: QTCREATORBUG-10791
Change-Id: I95721711a37e63c4c7c38e275089d6de0bb92bec
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
Rarely needed, but cheap to produce and nice-to-have in some cases.
Change-Id: Ib28e34a8085a4e0ed943646321843eea1bf4e138
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Also, converted non-breakable spaces into .
Change-Id: I3cf7f3b1bc3a5bd90219ea5ffa794411d5c8bc85
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Apparently the QML engine also loads pictures for invisible Image
objects. The pictures icons for examples and tutorials on the welcome
screen thus always try to load an extra video icon, which always fails.
By setting the URL to an empty string if the example or tutorial being
loaded is no video we can avoid that.
Change-Id: Ibafc11ed233f386bbbf1e7a4830fcb34bc1cd55d
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Aparrently clipping is slow in QML, so we use elide and manually control
visibility instead.
Change-Id: Idb743a8daec04b028f103a075a5416729f0e2a16
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
By tying the scroll offsets and visible areas of the two scrollable
elements together we avoid excessive loading times for the examples.
Change-Id: I6522ef3e6c0454e5bb05bef143953d8d1850ffdc
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
The integration was only doing that for breakpoints, but not for
stepping etc.
Task-number: QTCREATORBUG-10813
Change-Id: I4be7ec691e839bf062ab67587062cba00cc85e4f
Reviewed-by: hjk <hjk121@nokiamail.com>
This will need to be replaced with the results of the import scan, but
that will be for 3.1.
Change-Id: Icd398282142972421044c3b4d05fec9057cff95c
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Previously the correctly gdb-identified dynamic types were overwritten
with the value's static type. This is probably because the dynamic type
doesn't include the "&" for "reference". That, however, can easily be
fixed by just appending "&". As we're only handling references there it
should be safe to do so.
Task-number: QTCREATORBUG-10888
Change-Id: I7310916ce662956e66491423ad26658c32c8776b
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
