Reviewed-by: Trust Me

Conflicts:

	src/libs/cplusplus/CppBindings.cpp
	src/libs/cplusplus/CppBindings.h
	src/libs/cplusplus/FastPreprocessor.cpp
	src/libs/cplusplus/FastPreprocessor.h
	src/plugins/cpptools/cppcurrentdocumentfilter.cpp
	src/plugins/cpptools/cppcurrentdocumentfilter.h
	src/plugins/cpptools/cppsemanticsearch.cpp
	src/plugins/cpptools/cppsemanticsearch.h
	src/plugins/duieditor/parser/qmljs.g
	src/plugins/duieditor/parser/qmljsast.cpp
	src/plugins/duieditor/parser/qmljsast_p.h
	src/plugins/duieditor/parser/qmljsastfwd_p.h
	src/plugins/duieditor/parser/qmljsastvisitor.cpp
	src/plugins/duieditor/parser/qmljsastvisitor_p.h
	src/plugins/duieditor/parser/qmljsengine_p.cpp
	src/plugins/duieditor/parser/qmljsengine_p.h
	src/plugins/duieditor/parser/qmljsgrammar.cpp
	src/plugins/duieditor/parser/qmljsgrammar_p.h
	src/plugins/duieditor/parser/qmljslexer.cpp
	src/plugins/duieditor/parser/qmljslexer_p.h
	src/plugins/duieditor/parser/qmljsmemorypool_p.h
	src/plugins/duieditor/parser/qmljsnodepool_p.h
	src/plugins/duieditor/parser/qmljsparser.cpp
	src/plugins/duieditor/parser/qmljsparser_p.h
	src/plugins/duieditor/parser/qmljsprettypretty.cpp
	src/plugins/duieditor/parser/qmljsprettypretty_p.h
	src/plugins/duieditor/rewriter/rewriter.cpp
	src/plugins/duieditor/rewriter/rewriter_p.h
	src/plugins/duieditor/rewriter/textwriter.cpp
	src/plugins/duieditor/rewriter/textwriter_p.h
	src/shared/cplusplus/ASTClone.cpp
	tests/manual/cplusplus/main.cpp

There was still some "smartness" that made uppercase characters match
case-sensitive, regardless of the case-sensitivity setting. This annoyed
or at least confused many people who prefer case-insensitivity.

Reviewed-by: con

- clear up some Q_OS_LINUX vs. Q_OS_UNIX
- clear up Q_WS_* vs. Q_OS_* (relatively theoretical exercise)
- use proper #if-#else cascades instead of free-standing #ifs

HTML escaping was moved out of the TypePrettyPrinter since it interferes
with other logic there. Instead, the region to mark is now available
from the Overview and used by the FunctionArgumentWidget to put the
current argument in bold.

Was missing in commit efc0b208.

Reviewed-by: Roberto Raggi

Only attempt to activate the completion when there is a function id on
the left of the parenthesis.

Reviewed-by: Roberto Raggi

Since we're automatically inserting several kinds of brackets, but not
braces ({ }).

As this is how it is navigated by keyboard.

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

In case the completion shortcut contained the escape key (Mac xcode-like
shortcut settings).

Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

isValid -> supportsEditor

Was always on the first screen since the screen number was determined
incorrectly. Thanks to Christian Hönig for reporting the issue.

Reviewed-by: Daniel Molkentin

This is for the case of function overloads where one overload takes no
parameters. Solved by keeping track of the duplicate count.

Done with Roberto Raggi.

Done with Roberto Raggi.

Done with Roberto Raggi.

Done with Roberto Raggi.

Done with Roberto Raggi.

For example, don't keep triggering scope completion on bunch of colons.

Done with Roberto Raggi.

Done with Roberto Raggi.

We now hide the parent QFrame while updating the label to work around
the problem where the it wouldn't shrink the widget.

Done with Roberto Raggi

Now that we're showing this thing instantly, we can no longer rely on
the thing hiding cause of a focus change.

(cherry picked from commit 5a0a084c)

Conflicts:

	src/plugins/cpptools/cppcodecompletion.cpp

Now it shows immediately when there is only a single signature of a
given method/constructor.

(cherry picked from commit 8b9dd766)

Conflicts:

	src/plugins/cpptools/cppcodecompletion.cpp

Deals with cases like "QString s(", but for the moment doesn't handle
yet "QString const s(".

Done with Roberto Raggi.

(cherry picked from commit fca3ec1f)

When completing, don't insert "();" characters when they're already
there. Skip them instead.

(cherry picked from commit 86427ecf)

Conflicts:

	src/plugins/cpptools/cppcodecompletion.cpp

Crashed for example in the case of template instantiation. To make sure
the Function* stays valid, we need to not only keep around the Snapshot
but the whole LookupContext.

Done with Roberto Raggi.

Now that we're showing this thing instantly, we can no longer rely on
the thing hiding cause of a focus change.