Version: 4.2.1 (using KDE 4.6.0) OS: Linux As shown at the bottom of the "Adding new classes and member functions" section here: http://userbase.kde.org/KDevelop4/Manual/Working_with_source_code#Adding_new_classes_and_implementing_member_functions and in this snapshot http://userbase.kde.org/File:Kdevelop-37.png there is a problem with the auto-completion tooltip when starting to implement a new member function: the same member function is listed twice. I don't think there is a difference between choosing either one of them in terms of what it expands to but the fact that you get the same entry twice in the list is a bit confusing. On a side note, the tooltip doesn't work if there are more than one version of the same function (i.e. it is overloaded on the argument type), in which case the tooltip only offers one. Similarly, in that case, it would be useful if the tooltip showed the argument list to allow selecting the right one. Best & thanks W. Reproducible: Always
you probably mean this screenshot - right? http://userbase.kde.org/images.userbase/thumb/9/9c/Kdevelop-36.png/500px-Kdevelop-36.png anyhow I cannot reproduce it as easily as you suggest - please attach the code to your example. This works for me: class foo { void bar(); }; // now write "foo" and see that it will offer implementation of bar only once
adapting meta data
(In reply to comment #1) > you probably mean this screenshot - right? Yes, sorry for the wrong link. > anyhow I cannot reproduce it as easily as you suggest - please attach the code > to your example. This works for me: > > class foo { > void bar(); > }; > > // now write "foo" and see that it will offer implementation of bar only once Hm, with 4.2.0, I get two entries bar(). I'll attach a picture in a second. Was this fixed before 4.2.2? W.
Created attachment 60402 [details] Screenshot Image with the two occurrences of the same function in auto-complete. Sorry for the icon on the return type of the function -- it's supposed to read "void" but is an artifact of taking a screen shot...
Trying this again, with the same code as shown in the screenshot, I find that the bug is fixed in 4.2.2. Closing. Thanks W.