GNOME Bugzilla – Bug 597016
Scope not hidden in todo list
Last modified: 2010-10-09 08:19:39 UTC
In version 1.6.1 and earlier, even if HIDE_SCOPE_NAMES is set to YES, todo items relative to methods are listed with the full class scope. I'm attaching an example header and a Doxyfile (all defaults except EXTRACT_ALL=YES, HIDE_SCOPE_NAMES=YES and SORT_BY_SCOPE_NAME=YES.) The resulting todo list is Class Bar todo 3 Class Foo todo 1 Member N::Bar::baz () todo 4 Member N::Foo::bar () todo 2 The namespace N is correctly hidden when the todo item refers to a class, but is shown when the item refers to a method.
Created attachment 144518 [details] Test case
Confirmed. Should be fixed in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.6.2. Please verify if this is indeed the case and reopen the bug if you think it is not fixed (include any additional information that you think can be relevant).
You might have trimmed too much scope. Now the todo list looks like: Class Bar todo 3 Member bar () todo 2 Member baz () todo 4 Class Foo todo 1 Shouldn't the members be qualified with the class name, i.e., Foo::bar and Bar::baz? Or is this by design?
Still a problem in windows 1.6.2. Please increase Severity.
HTML output: In version 1.6.2 the "todo.html" and "bug.html" is generated, and the context of the files are OK, but the todo and bug in "explore_bar" don't have the right reference, in my case a00227.html and a00228.html.
(In reply to comment #6) > HTML output: > In version 1.6.2 the "todo.html" and "bug.html" is generated, and the context > of the files are OK, but the todo and bug in "explore_bar" don't have the right > reference, in my case a00227.html and a00228.html. The problem is related to the "SHORT_NAME" option in the Doxyfile. If disabled I don't have the problem.
The problem seam to be fixed in SVN version 724.
I'll mark the bug as assigned, so it will be closed with the next release.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.0. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.
Veryfied OK. Fixed in 1.7.0.
The problem reported by Poul-Erik Hansen in comment 6 might be fixed (I didn't check.) However, the original problem (the one reported in comment 4 before the issue was hijacked, see above for details) is still present in version 1.7.0.
Confirmed. In the next subversion update it should be fixed properly once and for all (hopefully ;-)
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.1. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.
Confirmed as fixed.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.