The default drag range is based on the minimum and maximum,
but sicne those are huge we overide the default.
Change-Id: Ibad785b475adfd92a78e6c5ff21fed2af21d637a
Reviewed-by: Henning Gründl <henning.gruendl@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This feature is useful for the bare-metal programming. It allows
to view the peripheral registers of the debugged device using
the GDB.
An information about the peripheral registers for a concrete
device contains in a special SVD file. A format of this file
described e.g. here:
* https://www.keil.com/pack/doc/CMSIS/SVD/html/svd_Format_pg.html
This feature supported only for ARM devices, and an appropriate
SVD files can be found in the Internet, also this files provides
by KEIL or IAR EW IDE's.
A use case in QtC is that the user should to choose desired SVD
file and set its path to the bare-metal device configuration widget.
After this, the user can enable the "Peripheral Registers" view,
choose a desired register group and to see a peripheral register
values.
Currently the following basic features are implemented:
* Choosing SVD file for a target bare-metal device.
* Choosing any peripheral register group, which is available for
this device.
* Seeing the info about the each peripheral register and its fields.
* Seeing the value for the each peripheral register and its fields.
* Changing the value for the each peripheral register and its fields
(if it is allowed by access for a concrete register or field).
* Changing the format of the values (hexadecimal, decimal, octal,
binary).
Fixes: QTCREATORBUG-18729
Change-Id: I3c38ea50ccd2e128746458f9b918095b4c2d644a
Reviewed-by: hjk <hjk@qt.io>
It's a widget containing a single widget with zero margin.
Use the inner BuildStepListWidget directly.
Change-Id: Ib2e6d63d4dbc570f45e287b216e0a9cfd5c5b8a1
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
...without the user having to add them to DISTFILES or OTHER_FILES in
addition to TRANSLATIONS.
Task-number: QTCREATORBUG-7453
Change-Id: Ic9621e66079a52f22272c945b92d183eec852f68
Reviewed-by: hjk <hjk@qt.io>
We have only one id for the steps, so short of coming up with some
fancy upgrade mechanism, stick to the one kind of step, but also
use only one factory, and do the switch in the step constructor
based on the nature of the parent buildsteplist.
Change-Id: I8fcc599682840d61e4a7f8b6fb7b792aafdd8766
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
... before announcing it and trying to remove it a second time.
Change-Id: I0f0238974fa317051d99b8f096cfc472e4f0cbe3
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
The only shared thing is an id, and even that's arguably even better
done by an enum, since there's a fixed set of three of them in that case.
Change-Id: Ia9da858524a5eb44eb91512ce72105249b5a9702
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Besides the announced change to QObject guts in a5a859e72 there has been
at least 6e0b5dadc and possibly more, so give up here.
Change-Id: I84201cef9f2a7515f082f4c3310bdc96f7a4216d
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The models hold essentially duplicated information besides the actual
configuration lists that are already in the target and are only
used in a context where the target is known and accessible.
As the models keep track of all added or removed configurations
and can be fed configurations of the right types only, the need
to filter is gone.
Change-Id: Iec2c6879223893297c71e7632310ac526b704237
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Targets are different from {Run,Build,Deployment}Configurations,
both regarding the level in the ProjectExplorer hierarchy, and
also by the set of supported operations (e.g. aspects).
Change-Id: Ia8490e2280a9ecc518395c5e48ce2fd5d6d58fd2
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Also fix typo and use Utils::filtered instead of creating a full copy
and removing unwanted items one-by-one.
Change-Id: Ibcdd4776cdf26ab1da5564cca0b99be83b208de2
Reviewed-by: Marco Bubke <marco.bubke@qt.io>
The build of a custom qml2puppet was failing, because
of utils/algorithm.h missing.
We should minimize Qt Creator dependencies in the puppet.
Change-Id: Iba8dd1a3979dbeeb1bfa860b50ba586bea20c7a7
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
In cc9d246b02 we started passing "-target"
to Clang when retrieving built-in header paths, but Clang doesn't like
that for iOS targets if we do not also pass the target architecture.
Fixes: QTCREATORBUG-22784
Change-Id: I007bba8ff14d7f303d84db2c803165ba789a5531
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
Needed because of conflicting patches went in
nearly at the same time.
Change-Id: I042637438d1b4e412ae39bc2e8bc5e1aa24527dc
Reviewed-by: André Hartmann <aha_1980@gmx.de>
Some QRingBuffer member got removed in 8f92baf5c9.
Change-Id: Ie0066db3b61bff25751a4886cb4b584cc4db49bf
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
..and use it in the Help plugin to open online help.
Change-Id: Ic84c63257a08b3c2ac76bedc0db04f297f695291
Reviewed-by: Tasuku Suzuki <tasuku.suzuki@qbc.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Handle environment changes in cmake better.
Server-mode will trigger an reader-change when the environment changes.
This has not been considered so far and a reader-change triggered by
an environment change was considered an error (and ignored).
Change-Id: I2d0baadbcfc86e04348c75d8e5997817bdc233a5
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
The typical use case is to add header/source file and then update
the CMakeLists.txt file to add the source.
Request a filesystem scan when a cmakefile changes to pick up the
header file when the source file is added.
Task-number: QTCREATORBUG-22674
Change-Id: Ifbb1ba37dd46967215f51db2c6ad92af669df585
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Do not overload the "new reader" logic with the logic for "no CMakeCache.txt"
file.
This makes it a bit simpler to reason about the different conditions when the
options are applied.
Note that "no CMakeCache.txt" is handled later anyway by adding the
"REPARSE_FORCE_CMAKE_RUN" flag.
Change-Id: Icc9455152053911cc839a19c76d3c0e44fc76fcf
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
We have to use lastSourceLocation().end() instead of offset.
SourceLocation was refactored and this was forgotten.
Change-Id: I6a43b42b48e03b6b289173a85f5a4a98b2a44628
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Quick tests allow definition of more than one TestCase inside a
qml file and even nesting is possible, so support this correctly.
Fixes: QTCREATORBUG-22761
Change-Id: I65fcc7cd6063d976d798c3e900d3299a12e2d73f
Reviewed-by: David Schulz <david.schulz@qt.io>
OriginControl replaces ExtendedFunctionButton with a combination of
ExtentendedFunctionLogic and a standalone ActionIndicator. Also changes
width and height to current style guide.
Change-Id: Idcad01505b1a61964a9a11c3b71c948c6d2a8d7b
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
* Add background radius property to AbstractButton
* Use AbstractButton instead of Controls 1 Button for
GradientDialogPopup
* Remove a few unnecessary imports
Change-Id: I02e0c5f198bd701d144effc5a574fc247182ffb4
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
