Besides Baremetal, Qt for MCUs also supports FreeRTOS for a few targets.
This change:
- shows the FreeRTOS source path chooser
- set the FreeRTOS source path as kit environment variable
- sets OS=FreeRTOS in the kit CMake configuration and kit meta data
Task-number: QTCREATORBUG-23938
Change-Id: I69cbd4f9b6b4a842788a8dad57905ef517b8b1d5
Reviewed-by: Rainer Keller <Rainer.Keller@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
The "canvas"/"scene"/"stage"/"working area" is called "Form Editor view".
Library, Navigator, Projects, Properties, States, Text Editor,
and Timeline are also their own views that can be organized as
workspaces and open from the Windows menu.
There are "tabs" only within views, and "panes" refers to
output panes.
Change-Id: I55898eef99b87245e4ab9b0163943725a90615a3
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
From Qt Design Studio 1.4. Add .qdoc and .qmlproject files,
quoted .qml files, and .png files.
Edit the files as necessary to reflect changes in version 1.5
and to reduce image file size.
Task-number: QDS-1519
Change-Id: I3bbdec0d3b4acf904c0008d1566dad13707e9851
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
- Added Global Annotation Status for files
- Added Status into ModelNode
- Slight rework for annotation dialog .ui classes
- Workaround for QmlJsLexer changes with Comment::deescapedText
Task: QDS-2027, QDS-2057
Change-Id: I609076110589fbeca1d8c45d049da9d433085a35
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
If pre 4.11 settings are present, this might lead to updated settings
being written at startup.
The code that writes settings indirectly uses the CppToolsPluginPrivate
instance via the "d" member of CppToolsPlugin. So this code path crashes
if triggered in the constructor of CppToolsPluginPrivate, since at that
point "d" cannot be assigned yet. Separate construction and
initialization to avoid this.
Fixes: QTCREATORBUG-23916
Change-Id: I0cb8a08bd9aa051679b71b06f569c44d2faab5a8
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
- "copy_directory dir target_dir" copies the contents of "dir" into "target_dir"
so we need to specify "include" at the end of the target directory
- copy_directory creates directories as needed
Fixes code model and analyzer errors when running without previous deployment
Fixes: QTCREATORBUG-23910
Change-Id: Id63dd790f89f720593cd0508241f79dfaddac794
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
When installing Qt for MCUs via the SDK installer, the user (in many
cases first-time evaluator) has to create the kits for Qt for MCUs. For
those who see Qt Creator for the first time, it is difficult to find out
where to search for the UI that generates those kits.
Let's help the user with an InfoBar entry that in case of ...
* McuSupport plugin being enabled (by SDK installer)
* Settings key [McuSupport]/Package_QtForMCUsSdk set (by SDK installer)
* Absence of valid Qt for MCUs Kits
... helps to directly open the right page and tab of the Options dialog.
Task-number: QTCREATORBUG-23943
Change-Id: I7d4834633b1b94ef663d62cd395ee071bd123f1f
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
So this can be used with a Qt 5.15 build
outside of QtCreator.
Change-Id: I691687bf661be21d9c28f13a52ff5df58bb7412a
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Calling m_rewriterView->clearErrorAndWarnings() has side effects
that can call back to the model and meta info system.
As a consequence meta info data based on the old document is created.
This can lead to a crash when the new document is set and
the old document is released.
Change-Id: I47de904914c1daa8d4a76aa1889f90bd86a07af7
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
... to "off".
The vast majority of people do not want to open their application in a
terminal just because it happens to be a console app.
Change-Id: I1372685f878349e7d16d9a06a75bcc4fd4f3c977
Reviewed-by: hjk <hjk@qt.io>
Can be useful to perform tasks that don't have
a dedicated UI in Creator.
In my setup, git bash was directly in the git
installation folder %ProgramFiles%\Git and
therefore one level above git.exe itself.
Change-Id: I1ca0d3439690170d7fb840bca17e2c412effe0a4
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
We already have the GroupItem.
This patch allows to automatically group items in a GroupItem.
The option is not visible if studio components are missing.
Task-number: QDS-1254
Change-Id: I64da7ec574426c9275fd29e131a1b1d761bf4299
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Let the user decide whether their pasted content is public. Default is
non-public, for safety reasons.
Task-number: QTCREATORBUG-23972
Change-Id: I5be444807d3f2cb41c629825715f0eaaa50d34c7
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
To call this function from a thread we have to lock it. There is no test
because there is no reasonable way to doing it. Anyway, this code is very
simple, so there no reason to see that there is an error in it.
Change-Id: Ibe57ddf421bc60929993afedecbde8c8486eb4db
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
And fix that the "ts_all" target did not get the custom target prefix.
Change-Id: Iff6a5e328456f3d949c31f2e41b48c400fad773c
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
I've chosen to add the controls themes colors to the main color list for couple of reasons.
1.) Adding the colors to the main color list allows them to be used from the QML constants
file that defines the controls color theme, in turn allowing us to customize the look and
feel of all controls on a per theme basis.
2.) I have added new colors instead of using the existing ones because of the ripple effects
of modifying existing colors in the themes, i.e that often when you want to change one particular
color in the UI modifying the value of existing colors in the theme has the unintended consequence
of changing other parts of the UI. Thus adding a specific set for the controls allows us to have a
fine grained approach to modifying the controls in any theme without disturbing the other elements
of the existing UI theme.
Change-Id: I16fb0458c870d01f68ed626676a665117628c917
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
... by splitting up huge amounts of output and feeding it to the
formatter in more digestable chunks, with event processing in between.
This prevents a UI freeze in the case that a single file emits a large
amount of diagnostics and the build tool buffers the output (as ninja
and qbs do), which therefore comes in all at once.
Apart from keeping the UI responsive, this also speeds up execution of
the build step itself, as the remaining output can now be displayed
after it has finished. If another build step is started and there is too
much output pending to flush all at once, we discard the pending output,
in order to prevent the delay to accumulate.
Fixes: QTCREATORBUG-23944
Task-number: QTCREATORBUG-22914
Change-Id: I7cfef939a85bbd13730f607b0f83c36473b0e550
Reviewed-by: hjk <hjk@qt.io>
