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>
We have to ensure that currentColor is not set to early.
Change-Id: I243898e08adf2f68d037374cc6c8ff586b1d5d0d
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Previously the recent projects had an extra scrollview and the sessions
had a fixed height. In addition, as there will never be any scrollbars
around the recent projects anymore we don't need the borders around them
anymore, either.
Task-number: QTCREATORBUG-10731
Change-Id: I491265148a3ce777f15b8ba7d852248b583f2c83
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
the attached process is seen as still running just after the attach
and continuing fails, immediately later a spontaneous stop is
detected and on ios (where we set continueAfterAttach) we
continue after the spontanous stop.
This also work in the desktop case.
Change-Id: I92fbcd3ba319da7d9e664f67c8cbbea00f0daa43
Reviewed-by: hjk <hjk121@nokiamail.com>
Use native text rendering to get crisp fonts
Change-Id: I75ca9ae323f2e4bd60e080cdcc2a6d90f0234c33
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This only affects MinGW where the feature triggered QTCREATORBUG-5200 in
the past. Right now the performance impact of c9c0f80 (fixing
QTCREATORBUG-10826) is unclear and no time to investigate. Trading the
feature for robustness seems in order. Power-users can remove the return
line in the script to get it back.
Change-Id: If5a30808b72969493e5f40dd0fcbafdcccec343e
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
An unavailable display value doesn't mean an invalid index
Change-Id: I68baa09c9d6176dcd1a3f983ec375414292d7026
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
We probably should completely skip the code in the cases where Qt
itself already propagates the object name to the underlying threads.
Task-number: QTCREATORBUG-10826
Change-Id: I7e9e5b7c990a270c8563e40c1fe1e900724c1e5c
Reviewed-by: Ryan May <ryan.may@eecradar.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
Mark the qbs flavors of the plain C and the plain C++ project as
console applications.
Task-number: QTCREATORBUG-10815
Change-Id: Ic143ffe4026a97d0d27e0a85e62724b26e0ea5ce
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
We only need one scrollable element in the WelcomePage. By passing
the height properties of inner elements to the outermost one we can
avoid multiple vertical scrollbars next to each other. Since this
removes the QScrollArea around the welcome page it fixes
QTCREATORBUG-10796
Task-number: QTCREATORBUG-10796
Change-Id: I08b0409e21f16be6c3e0e5a58f2665320d0a14fe
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
