There is no need to split the output into separate lines
and search for port number in each line afterwards.
Search for port number in the whole output instead.
Change-Id: Id020bd5a73080be30b6cef47853e027235105ae3
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Operate now on QKeyCombination instead.
Return false if there are modifiers other than Shift or Keypad.
Otherwise, return the result of comparing key() with the Escape key.
Change-Id: Ica6409a7b7b5ed28e79915691c40a898008735f7
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
We do not need different code paths for Xcode < 9 nowadays.
Just tell simctl too boot the requested device and make sure the
Simulator app is running.
This also fixes an issue if for some reason a different device is already
booted without the Simulator app running, e.g.
1. make sure Simulator is not running
2. boot a device from the command line with
`xcrun simctl boot <deviceID>` (get the device ID from the Devices &
Simulators window in Xcode)
3. start Qt Creator and run an application on a *different* simulator
device
Without this patch Simulator app opens with the device from (2) and
deployment of the application fails for the different device.
With this patch the device for (3) is booted and the application
deployed and run.
Change-Id: Ifce8c470f2d4d646295ca4e47fbd92308f87adf8
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
If simctl fails, always include its stderr output in the error, if any.
Change-Id: I7a5643ac81befc9d0595e9c3bd4fa009057ff85b
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Allows a LSP plugin to dynamically configure the initializationOptions
Change-Id: Idc5d6526a732512b2e4e7394fb1c8b5749cde25d
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
It was set, but nobody was actually using it.
Change-Id: I99c6fcd4605591d65e5f3fb3f489a3de0c61fb24
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Instead, emit remoteProcessFinished() directly from the
startDebuggerServer() function. Make this function void.
Change-Id: Ibeeb2a1e3aabb9b3021203003e31a7b44eef573e
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Make the getconf process a yet another task in the recipe.
Change-Id: I4c25cb512740471fa603ee0b9a46a41879ba90cd
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Setting up a working emsdk requires a couple of steps:
1) Installation/clone of emsdk
2) Installation of an SDK
3) Activation of an SDK
If the setup is incomplete, Qt Creator cannot use the emsdk. Until now,
users got no explicit indication of an unsuccessful emsdk detection and
no hint of what could be wrong. This change adds visual diagnostics of
potentially missing emsdk setup steps.
Fixes: QTCREATORBUG-30057
Change-Id: I2dc2d3388be75e8586dc18d24b0a5b57bcffaadb
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
This removes the need for a delayed call of
WebAssemblySettings::updateStatus(), and a possible visual glitch where
too many widgets are visible for a split sencond.
Change-Id: I2b4b39f6576d16d4fde6b3e3df1ce09e6805086d
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
So people can at least add a custom build step
Change-Id: I78f3601233c776501bdc73fb7d67cbfeb886ced2
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
If someone wants to switch to a language because it is their native one,
it makes most sense to show the option in their language.
Nevertheless the english name is useful too, so keep it.
Change-Id: I3afb81202e6799525c1c9c503ac3a97c608c3c8a
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
