The design of the Projects mode changed several times. We wrote lots of
workarounds to keep even more old code alive because we never had the time
for a proper refactoring. This time is now.
Leads to more stable code with far less variables flying around.
Task-number: QTCREATORBUG-20265
Change-Id: I29e5956ea3279cdb1d6da61bf5b461666de436bc
Reviewed-by: Robert Loehning <robert.loehning@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Yes, there are only ten pastes per IP per day. But doesn't that mean that
nobody can rely on it being availabe anyway? So it's better to use some
of those ten pastes for testing instead of not testing pasting at all.
Change-Id: I45362e5ab0c3eb43f1ddd18d4be39474e26c8460
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The patch that removed Qt4 completely from the widget app wizard
has been reverted.
Adjusting the tests now.
Change-Id: I0af1eb2102caa22022658d1189794c7757c7628f
Reviewed-by: Robert Loehning <robert.loehning@qt.io>
This reverts commit 1a6522b47c
which leaves people wondering about their kit setups.
Creating a project that possibly does not compile due to the
use of C++11's nullptr in the generated code is lesser evil.
Apart from that this potential mis-compilation does not
happen in practice on e.g. Ubuntu 18.04 with system Qt 4
and system compiler.
Change-Id: Iaa90f225d5317dc48428aa2d3fcf3ec051ef2018
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
A empty path segment in LD_LIBRARY_PATH is *not* ignored and treated
as '.' IIRC.
So make sure to not leave a ':' in first place of LD_LIBRARY_PATH or set
an empty LD_LIBRARY_PATH on Linux.
Change-Id: I99ec2e333c6c0205334daf14ac6a2373c6e465ad
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Cancel processing the environment diff only if the setenv scripts return
a non zero exit code. Just checking the presence of standard error
output seems to be a to aggressive error checking in this case.
Task-number: QTCREATORBUG-18328
Change-Id: I9243932cd5721cfbfec5a980a2fab6e69f4c31c7
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
They are triggered a lot in Clang headers.
Change-Id: I31f31a4f52e269d773cf1b41ad52f279ee368c2e
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
Support for several controls has been added to the Library in the
Design mode.
Change-Id: I9822f7379991eea3b32f47574e3c3548445d538d
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
As QML currently does not expose a command to atomically enable or
disable a breakpoint, we need to remove and re-insert it. The previous
code scheduled the removal through a timer, and depending on if the
timer hit before the insertion or after, the operation was successful or
not.
As the QML engine doesn't have to be in a specific state to insert and
remove breakpoints, we can just directly send the messages instead and
therefore be certain that they arrive in the right order.
Task-number: QTCREATORBUG-20795
Change-Id: If69797b2c75e1107ad552f88e709e1580b4164db
Reviewed-by: hjk <hjk@qt.io>
Creator registers a "Collapse All" action for the Project tree. Make
this work again.
Task-number: QTCREATORBUG-20771
Change-Id: I49f1c8a97c4eb22ef6f7f703eefdfe46c3c0a035
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
They appear a lot in Clang headers. Until this is fixed in Clang, suppress
them.
Change-Id: I5292ae442089aec3f52ba846ee21e0bd9e61d0cb
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
If the root size is 0, none of the nodes will be visible. Don't create
them in the first place.
Task-number: QTCREATORBUG-20772
Change-Id: I9595daece2d17fe8202b322ffafd361d6fa422fa
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
If users need to register additional QML types before Qt5.12
they need to bend the Quick tests magic a bit and use
quick_test_main or quick_test_main_with_setup directly.
The plugin supports something similar for QTest::qExec, so
allow this for Quick tests as well.
Task-number: QTCREATORBUG-20746
Change-Id: I672f8410914c6cc77abc901998f419dda35755ae
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
The examples are put throw two proxy models. The first one implements
the sorting and filtering, the second one transforms the list into a
grid.
The grid proxy model was based on QIdentityProxyModel, which is wrong
because that explicitly states that it should be used when the structure
of the model stays the same.
Even QAbstractProxyModel works under the assumption that all items in
the proxy model correspond to an item in the source model, which is not
true for a N*M grid.
Just implement the proxy model "by hand", making sure that all items
that cannot be mapped to the source are handles correctly as "empty"
items.
Task-number: QTCREATORBUG-20641
Change-Id: Id08b77bb7157b893b9d0d73dc006db98d90032b7
Reviewed-by: hjk <hjk@qt.io>
Fix crash when updating the parsing state of a project during the time
between the project being removed from the session and the time when
the project is actually destroyed.
Change-Id: I54bf4793626497315fe588ebb68474b880de2984
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
If you turned off Designer and ScxmlEditor plugins, you'd not get Design
mode even if you have Qt Quick Designer.
Fix-up of 299da01332
Change-Id: Ib3a269db9630af09c36968435ca0b0d998cc1709
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Modifying C++ files of Quick tests had been ignored as they
normally have little impact.
But nevertheless this behavior is wrong and could lead to
unexpected behavior later on if no complete rescan had been
done and even with a rescan there could have been some
cached artifacts.
Fix this by tracking the paths of the C++ files that hold
the main() or the respective macro to be able to handle
changes of these files correctly as well.
Task-number: QTCREATORBUG-20746
Change-Id: Iec860aa63ffd167511efdbf63a6ffa369f094edf
Reviewed-by: David Schulz <david.schulz@qt.io>
Move the topic up in the hierarchy. Will remove "Creating Screens" in
a follow-up commit.
Change-Id: I0de2bdc4706ab0cce13f5772006126b291e76b97
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
If something fails while extracting the build env from msvc vavars
scripts we want to add task hub entries to inform the user about a most
probably unusable toolchain. As the msvc toolchain detection is threaded
nowadays and the TaskHub is not thread safe we need to propagate the
error message to the main thread before adding the Task entries.
Change-Id: I5c67d3b8d58b22ea895afb6f22ee73f19fa52f17
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
If qmake uses /usr/bin/gcc and the kit is configured to use /usr/bin/gcc-7,
and both reference the same executable, there is no reason to warn.
Change-Id: Ida79fccb97cffb682c1d85d7fa8888d85bf7d6a4
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Now that the states have their own topic, all information
about using states should be found there.
Change-Id: Iab1d17aeca9774e3e4bd3e50c776862aa4697a47
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Like for the llvm code model additional 3rd party installation is
required to build the python enabled dumper on Windows. Adding minimum
version of Python and the name of the environment variable pointing to
the Python installation to the README.md.
Change-Id: I0cad39a57e4726083fcd44bde8b4c990cbd1ab03
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
