The icons were scaled down and became really muddy on low dpi screens.
With Hennings additions we create high dpi versions behind the scene
in any case.
Change-Id: Iab94989b6cfae7b5cefcd7bcded4efa3a1d35a6f
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Add the optional QtQuick3D dependency that was so far only in the qmake
project file. Also fix annoying moc warnings for builds without
QtQuick3D.
Change-Id: Ic0f4f3de5b4a5d715332166d7390ad027dd377ed
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Don't limit this functionality to files that are part of the snapshot,
but try to open all files. This will allow opening c++ files defined in
a qbs project file.
Fixes: QTCREATORBUG-22685
Change-Id: If2a2a2075e5d7113a7bb44625c0f29ef66138d3c
Reviewed-by: Denis Shienkov <denis.shienkov@gmail.com>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Add the applitcation dir path to the path environment variable
if jom cannot be found there. This should fix the cannot find
jom error for binary releases since we ship jom with qc.
Fixes: QTCREATORBUG-22645
Change-Id: Ia3b55f794d3ac4b5fd6d2e85cf19f00bd8cddd2c
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Only search for the jom cmake generator if this setting is
enabled.
Change-Id: Id8eed91d47f1f6ca2375fe0d169b21168c5ca4ff
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Disable the timer to be safe. The issue is bothering us for a
very long time and we were not able to find the real
cause.
Task-number: QDS-343
Task-number: QDS-1984
Task-number: QTCREATORBUG-20364
Change-Id: I5023f27be25ba7971db80990eeb9562fd63dc15d
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
After benchmarking it on a i7 it was 20% faster in release.
(in debug even more)
Change-Id: Ibf4599813c2e3bc206ea77dea7fc972018554b09
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Include paths and headers were missing for building a separator
Qt Quick Designer plugin.
Task-number: QTCREATORBUG-23778
Change-Id: Ib6ba96ad42a8b2b36e0ee2f0e3c51c27f3365d37
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Quick3D importer caches various things when it does the import, making
reusing the instance for multiple imports error prone.
Change-Id: I6e8e3dedf579683cdda58624172395a392f4e567
Fixes: QDS-1960
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
In case sensitive file systems, revert to old capitalization
after reimporting existing asset with different capitalization.
Change-Id: If26443b34e408c84aeb12940262c8b9f696f0bbf
Fixes: QDS-1958
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Item library thumbnail and navigator icon are refreshed if asset is
reimported, and the puppet is restarted in case the asset is in use.
Change-Id: Ic5577eff3a24bcce87b504e9c059c29f6cb887a5
Fixes: QDS-1957
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
... and add some translation hints. Looks like a more natural
place to live in.
Change-Id: I3e8917d826baaa7277dde744f3843d5ab7fe0afd
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Now only one piece of code needs to be written to both linkify output in
an output pane and create tasks for it in the issues pane.
The calling sites are also simplified. For instance, until now, build
steps had to feed their output parsers manually and then push the
created tasks up the signal stack in parallel with the actual output,
which the build manager relied upon for cross-linking the output pane
content. Afterwards, the output would get forwarded to the formatter
(and parsed for ANSI escape codes a second time). In contrast, a build
step now just forwards the process output, and task parsing as well as
output formatting is done centrally further up the stack.
Concrete user-visible improvements so far:
- File paths in compiler/linker messages are clickable links now.
- QtTest applications now create clickable links also when run
as part of a build step, not just in the app output pane.
Task-number: QTCREATORBUG-22665
Change-Id: Ic9fb95b2d97f2520ab3ec653315e9219466ec08d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
In particular, we do not want to follow symbolic links, but see the file
names as they appear in the project file.
Fixes: QTCREATORBUG-23511
Change-Id: Ibf83ac143933fa0c9568dd4e3c0be825d8ba8f0b
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
The UVSC support the debugger commands execution feature
using the UVSC_DBG_EXEC_CMD function. This function non-blocks
if an command execution fails. So we can use this function to
execute a breakpoint insertion command:
* http://www.keil.com/support/man/docs/uv4/uv4_cm_breakset.htm
But, to get the properties of the inserted breakpoint we need to
enumerate all available breakpoints and to find the desired
breakpoint by its expression.
Besides, we need to fix and the 'expressionBuffer' field of the
BKRSP structure according to the original UVSC API.
Change-Id: I3c52e8955de28180aaafa1af9f6001ff6ee3b7fb
Reviewed-by: hjk <hjk@qt.io>
- Remove information about enabling the Timeline view, because it
is now enabled by default
- Update the screenshot to show the animation curve editor icon
- Show information about previewing, which is now enabled
- Fix UI text for the animation curve editor
Change-Id: I288b45f521945aadf76475871f422ccb41cd1ac1
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Sometime the UVSC_DBG_CREATE_BP function stalls within 10 seconds
and then returns with the timeout error.
But this problem can be avoided by creating and then removing the
fake breakpoint before creating the original breakpoint. In this case,
we need to remove the line number from the expression of this fake
breakpoint.
Of course, it does not help when the breakpoint cannot be created
with the specified expression. In this case the UVSC_DBG_CREATE_BP
function will stall anyway within 10 seconds.
Change-Id: Ie8d39c545683d6bb3e29e5bb7c4ac0fd1e34222a
Reviewed-by: hjk <hjk@qt.io>
The build directory going to get set up either in
doInitialize or in fromMap, both using magic hidden in
BuildConfiguration itself.
Change-Id: I1aeb59f56d63f0affd50b45cc937e606af6da7b4
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
For this to work, we need to make sure no parsing is triggered before
the project is fully set up. Otherwise it would be QTCREATORBUG-23816
again...
Change-Id: If81f4c6b9c82283abdaa8a635f93ebe0bcaf8159
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Tealeaf mode has been removed, so update the documentation accordingly.
Change-Id: Ibecc2f127f3acb5d6813e4f670c3424db633cacb
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Tealeaf reader mode has been removed, so require at least
CMake version 3.7 (which comes with server-mode).
Change-Id: I1ce8cdd08f226446ccca5882d1cb2171019b3409
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
