Bad idea to hardcode the background color. Now using the style directly
to draw a fake tooltip as background for the function argument hint.
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@nokia.com>
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.
In case the completion shortcut contained the escape key (Mac xcode-like
shortcut settings).
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>
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.
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 5a0a084c31)
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 8b9dd766c8)
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 fca3ec1f32)
When completing, don't insert "();" characters when they're already
there. Skip them instead.
(cherry picked from commit 86427ecf62)
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.
