Do not show the "commit message is short" text while
the user is still typing the first words.
Therefore, make the initial timeout larger and restart
the timer whenever the submit message changes.
After the minimal subject length or a newline is entered,
switch to faster evaluation.
Change-Id: I41034ed2c8e71e81dae42685bc9ff310edca2543
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Use the QFontMetricsF constructor instead.
(Which I hope this change does as requested by the warning)
Change-Id: I89992715f5cc0a2e1b5e98498c2cc36bb705b187
Reviewed-by: hjk <hjk@qt.io>
See the CMake documentation https://cmake.org/cmake/help/latest/
prop_tgt/FOLDER.html
This allows placement of targets in the project view in specific folders
like e.g. "tests"
Qt Creator (ab)uses the FOLDER property for the "qtc_runnable" feature,
see https://doc.qt.io/qtcreator/creator-run-settings.html
which would not allow to have both.
The "qtc_runnable" should be fixed by having a property "QTC_RUNNABLE"
for a target and have Qt Creator parse the code.
Fixes: QTCREATORBUG-28873
Change-Id: I73433de78b9a86f631ee9d7903db535b69b734f6
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
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>
The context menu kept a handle on the editor and document, and these
could be deleted behind its back. Use QPointers to actually check.
Fixes: QTCREATORBUG-31232
Change-Id: I613abbe6dc0fbac60c2e527f715a7b8c2f083893
Reviewed-by: Christian Stenger <christian.stenger@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>
