GitLab

Task-number: QTCREATORBUG-3993

Reviewed-by: Kai Koehne

Conflicts:
	doc/qtcreator.qdoc

Task-Nr: QTCREATORBUG-3886

- Introduce a shared analysis output pane using a stacked widgets,
  layouts for the tools' output panes and toolbar widgets.
- Introduce IAnalyzerOutputPaneAdapter interface returned
  by IAnalyzerTool to manage them.
- Remove mode and its mainwindow contents (depending on enum
  constants should use cases for it occur).

Reviewed-by: con

Merge-request: 267
Reviewed-by: con <qtc-committer@nokia.com>

Remove S60devices and all the code surrounding it. This gets rid of
the S60 devices tab in the options dialog, too.

Tasknumber: QTCREATORBUG-3681
Reviewed-by: dt

* Save ABI in toolchain
* have guessGccAbi return a list of possible matches.

Tasknumber: QTCREATORBUG-3996
Reviewed-by: dt

Reviewed-by: dt

silences a qt warning.

Reviewed-by: Erik Verbruggen

Project directories should come before system directories.

Task-Nr: QTCREATORBUG-3959

given that checking for a match is expensive and determining the
priority is cheap, it makes sense to match only if the priority is known
to be high enough.

Reviewed-by: Leandro Melo

Reviewed-by: Leandro Melo

simply add
  CONFIG += depend_includepath
to qtcreator.pri and remove all the manual DEPENDPATHs, as half of them
were missing anyway, and i wouldn't expect it to ever change. not
touching src/shared/ for syncing reasons.

they are a bit misleading (and embarrassing ...)

Reviewed-by: Kai Koehne

Better safe then sorry.

Adding missing tooltips

Task-number: QTCREATORBUG-3525

Task-number: QTCREATORBUG-3733

Task-number: QTCREATORBUG-4001

Reviewed-by: Kai Koehne

Ubuntu comes with only a stripped down version of vim by default which
doesn't support setting the column. So we don't do it.

Task-number: QTCREATORBUG-3850

This reverts commit 9eccbbee.

After a bit more discussion and considering
2c4eb251 this wasn't a good idea after
all.

If on F1 no documentation was found, the focus was not set to the side
bar, making it impossible to press F1 again to get into help mode.
The fix also makes sure that the "blank" page is not set to the help
mode in this case, to avoid a big white empty area.

otherwise the initial value set before the kind was set will be
displayed as validated by the default kind's rules.

it's well within expectations that they do not exist at the time of
configuration (especially when shadow building).
additionally, keeping the validation info (macros and environment)
up-to-date would require a notification infrastructure which is just not
worth the effort.

no need to make a dummyfied derived class when using another flag is
just fine.

We use Qt now instead of Qt Quick

The properties x and y get removed when putting an item
into an positioner.