| Summary: | C++ code completion shouldn't popup if the current word exactly matches something in the list. | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Tim Hutt <tdhutt> |
| Component: | Code completion | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | david.nolden.kde |
| Priority: | HI | ||
| Version: | 3.3.94 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I find the automatic code-completion totally annoying whatsoever. Anyway there's a similar bugreport (http://bugs.kde.org/show_bug.cgi?id=127100) in which Jens clearly states that it is important to see that the method or variable exists. I agree with the reporter. Completion box shouldn't automatically appear if we already match something in it. It should still be possible to manually invoke it, of course. still a problem in kdevelop4 :( I'm wondering wether this is actually on our side or kate's side of things? Implemented now within kate. |
Version: 3.3.94 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux E.g.: QPushButton* mybutton = new QPushButton("A button"); connect(mybutton After you've typed that, there is no point showing a popup that just lists " QPushButton* mybutton; local" or whatever. It should not not show the popup if the current word matches one in the completion list. Just anticipating something: I don't think it should pop up even in this situation: QPushButton* mybutton = new QPushButton("A button"); QPushButton* mybutton_two = new QPushButton("A button"); QPushButton* mybutton_three = new QPushButton("A button"); connect(mybutton It should popup after some minimum number of letters (say after 'mybu') and then disappear when you get to 'mybutton' and then come back for 'mybutton_'. That is the least annoying method in my amazing opinion! Cheers