| Summary: | Two Classes view bugs | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | András Manţia <amantia> |
| Component: | classbrowser | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
1. Okay, after some investigation I found that this is happening because you have two Parser classes in the same namespace, but in different sub projects. The class view is only smart enough to handle one, so it finds the one in kommander/editor. I'm not sure how high of a priority it will be to fix this or if it is even considered a 'bug'. 2. Fixed in CVS..thank you. 3. Fixed in CVS also. Thanks. Hi, 1. Yes, indeed. I do not maintain Kommander, so I haven't realized the Parser class there. But I still consider it to be a bug, as it does not show correctly all the classes and because there are times when it appears in the classes tree... I don't have a way to reproduce it, but after working on the my parser class, which was not shown before, suddenly it appeared in the tree... Andras Subject: Re: Two Classes view bugs
> ------- Additional Comments From caleb@aei-tech.com 2003-01-01 03:25
> ------- 1. Okay, after some investigation I found that this is happening
> because you have two Parser classes in the same namespace, but in different
> sub projects. The class view is only smart enough to handle one, so it
> finds the one in kommander/editor. I'm not sure how high of a priority it
> will be to fix this or if it is even considered a 'bug'.
One more reason why this is a bug: the class view behaves wrong, even if we
say that it supports only one class with the name Parser in a namespace, when
you switch to "List by Namespaces". In this case under the Parser will appear
a mix of the two Parser classes methods, and:
1. clicking on the Parser node opens the first parser.h (from the kommander
subproject).
2. clicking on the Parser ctor opens the second parser.h and the corresponding
parser.cpp.
BTW it's pretty bad that subprojects are in the same namespace, as usually
they are not tighted to the main project, both works and can be released
separately, and as the classes with same name does not conflict during
compilation/linking/runtime, they shouldn't cause any conflict for KDevelop
either. Of course, it's possible to develop even in this case, but this is
definetly a bug. If you wish I reopen this bug report or create a new one
for this.
Andras
Reopening because this is indeed a bug that can be fixed. As far as I can tell, this now works fine with the new classbrowser. Closing. hmm.. konqueror is buggy. ;) moving to kdevplatform's classbrowser |
Version: (using KDE Devel) Installed from: Compiled sources Compiler: g++ 2.95.3 OS: Linux Three bugs in the Classes view: 1. I have the following structure in my project: quanta (dir) parser (dir) parser.cpp parser.h node.cpp node.h ... ... The parser.h contains the definition of Parser class and the node.h the definition of the Node class. Now in the Classes view I see Classes quanta parser Node ... ... So, the Parser class does not appear in the view. It does appear if I select List By Namespace, but the Project Options->Class View setting has no influence on it. 2. Under Structs the structs are listed, but they do not show their attributes. 3. Clicking with LMB on a struct opens the file where it is declared, but does not go to the definition line. MMB opens and goes to the right line. Even in the case of classes the old behaviour was more logical, but if you have chosen that LMB opens the implementation file, it should jump to the implementation of first method of the class. Andras