Those properties are QtQuick 2 only and were missing in the
property editor.
Change-Id: Ie58a4eac86b945bdde24d32fc373396268bb593e
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
The switch between compact/full display was so far part of the
individual dumpers, there's some potential for code-reuse here.
Change-Id: I47e3308cfd2209948adbf70fca617908e793c0fc
Reviewed-by: hjk <hjk121@nokiamail.com>
Make backend-agnostic and use it for QFiniteStack and
std::{array,vector}
Change-Id: I1702d4290ee24c957f77b539591313ac83021003
Reviewed-by: hjk <hjk121@nokiamail.com>
Correctly use the device specific cached symbols to avoid downloading
them from the device (big slowdown).
Task-number: QTCREATORBUG-10884
Change-Id: Ic82482e4b1dadf55f695a67fd420ac1b095a3ca1
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
This affects mainly Apple's version of GDB. Mac users are advised to
use LLDB, or some recent build of FSF GDB.
Change-Id: I6a7fbb591e79f737e12d08b0e881e9e4d1d9660c
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
I kept them as reference, but they are not needed anymore.
The QtQuick 2.0 port is done.
Change-Id: Ieb75d506a45636a17adc3c78d7beca6d5c1fd211
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
Since there are issues with transaction we play safe.
Task-number: QTCREATORBUG-11134
Change-Id: I2144f81f14046317d967d6644befeb74e8d27eb8
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
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>
