GNOME Bugzilla – Bug 577005
nested \defgroup commands do not work correctly
Last modified: 2010-06-15 11:21:46 UTC
Please describe the problem: I use an own file to define the structure of modules using multiple nested \defgroup's. In the headerfiles, I only use \addtogroup \ingroup or \weakgroup to add function definitions to the appropriate module. The resulting module hierarchy is not correct, even in a minimal example where only one file is present: /** \defgroup b B \{ \defgroup c C \{ \defgroup d D \defgroup e E \} \defgroup f F \} */ Running doxygen on this example (latest SVN version), gives a Module-page with the following hierachy: * A o B + C o D * E both in HTML and LaTeX-output. Obviously, E and D are misplaced, here. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 131514 [details] doxyfile used to produce the bug Sorry, I mixed up the labels. In the file, it starts with 'B', in the result with 'a'.
(In reply to comment #1) > Created an attachment (id=131514) [details] > doxyfile used to produce the bug > > Sorry, I mixed up the labels. In the file, it starts with 'B', in the result > with 'a'. I Have the same problem if i include my file where all groups are created like this : * \defgroup IdA title A * @{ * \defgroup IdB title B * \defgroup IdC title C * @} * \defgroup IdD title D in my generated documentation i have the group IdC between the group IdA and IdD For summary, i want : IdA IdB IdC IdD I have, for now : IdA IdB IdC IdD
I use doxygen 1.6.1 and i have the same problem since 1.4.7 (first i used)
Is anything going to happen to this bug? It produces the same result with the latest svn-version.
Hi Matthias, Thanks for bringing this to my attention again. I'll correct the probelm in the next release.
Great! This will help me a lot. I used the grouping feature quite excessively and was a bit disappointed about the result :-) Thanks a lot for the great piece of software!
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.