Bug 317043 - Wrong tooltip when function is overloaded
Summary: Wrong tooltip when function is overloaded
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: git master
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 18:58 UTC by xcojack@gmail.com
Modified: 2018-03-25 22:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description xcojack@gmail.com 2013-03-19 18:58:17 UTC
For example

check first link:
http://wstaw.org/m/2013/03/19/kdevelop-wrong-tooltip1.png
and now second:
http://wstaw.org/m/2013/03/19/kdevelop-wrong-tooltip2.png

and now, first function returns QString, next function as param takes QAction and returns void, but in code is a pointer to the KAction ;)

Reproducible: Always

Steps to Reproduce:
1. Overload function by parameter type
2. Call overloaded
3. Check tooltip
Actual Results:  
Tooltip to the first function declaration

Expected Results:  
Tooltip to the function with actual parameters type, parameters count...

I doesn't check what about when function is overloaded by more parameters.
Comment 1 Aleix Pol 2013-06-12 01:34:42 UTC
I've seen it, could be improved.
Comment 2 Kevin Funk 2018-03-25 22:19:14 UTC
We are working on a new clang-based C/C++ language plugin for KDevelop 5 which
supersedes the old C++ plugin in KDevelop 4. See e.g.:
https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available

Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather
want to supply a good Clang based C++ experience for KDevelop 5 than wasting
our time on the legacy C++ support for KDevelop 4.

With the new clang-based C/C++ language plugin, the bug presented here does not
occur. In my testing. For these reasons, I'll close this bug. Please stay tuned
for KDevelop 5.

If you think this bug is applicable to Clang/KDevelop 5, please reopen the
report and add new information on how to reproduce the bug there.