response was received

No functional changes for now.

Reviewed-by: kh1

Reviewed-by: kkoehne

Reviewed-by: kkoehne

Reviewed-by: kkoehne

Task-Number: BAUHAUS-535
Reviewed-by: kkoehne

Task-Number: BAUHAUS-617
Reviewed-by: kkoehne

Move actions into FancyMainWindow. Register them in
DebuggerUISwitcher and FormEditorW. Manually hide
Debugger actions for Non-Debug modes (as they belong
to the language context).
Acked-by: con

Fixes the broken topic chooser and keyword resolving.

Reviewed-by: ck

Allows completion of local variable and function names.

Task-number: QTCREATORBUG-942
Reviewed-by: Roberto Raggi

using the targetsetuppage.

Handle the deletion of temporary QtVersions properly. Remove
workaround.

Reviewed-by: dt

... so that we can sanity check.

Reviewed-by: dt

Reviewed-by: dt

... to a place where we can share the checks later.

This makes a task somewhat more useful outside of the
context of a taskwindow.

Reviewed-by: dt

Task-Number: BAUHAUS-606

Task-number: BAUHAUS-599

This is to keep the resources view in the same look as the
navigator view.

Strip '[', ']' off inames in coreengine so
that the name lookup for them works.
Handle 64bit-addresses in .dvalloc-output
parsing for dumpers. Some debug formatting.

Task-number: QTCREATORBUG-1216

unlike in qmake, the arguments are already expanded at this point
(which is strictly speaking a bug for the iterator variable name),
so it is plain wrong to call doVariableReplace on them.

amazingly enough, qlist::{first,last}() have non-const versions,
which are of course used when you least expect it ...

just for debugging ...

this produces qmake-like output when recursing

otherwise we may re-process subdirs multiple times in cumulative mode.