Avoids some annoyance for people using case-sensitive completion, when
unrelated completions items would get higher relevance because they
start with the typed string when matched case-insensitively.
In case-insensitive mode, a case-sensitive prefix match now does get a
higher relevance than a case-insensitive match.
Reviewed-by: con
Even when an upper case character can also match a lower case one, it
should only be treated as a CamelCase match when the matched character
is also upper case. This avoids some false positives.
Also, the part that allows a word in a CamelCase identifier to be
truncated should never be matched case-insensitively.
By default now only the first letter is case-sensitive. It is still
possible to choose full or no case-sensitivity as well.
Task-number: QTCREATORBUG-236
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>
When constructor completion was attempted on a base class specified in a
class declaration, a null pointer reference would occur.
Task-number: QTCREATORBUG-321
Reviewed-by: Christian Kamm <christian.d.kamm@nokia.com>
They should always use the function parameter tooltip.
This fixes a bug where you were offered completion for
C foo( -> C foo(int x)
if C had a constructor taking int x.
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>
Instead of just completing
void A::foo(|) -> void A::foo(int i|), we now complete
void A::foo(|) -> void A::foo(int i) const|
where | represents the place of the cursor.
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
(cherry picked from commit 202fef42ca)
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
The completion for the directory wasn't triggered because one of the
items matched the typed string, so the list of completion wasn't empty
and no new trigger was allowed.
By not matching items when a trailing slash is typed, the list is
allowed to trigger again from the new location.
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>
