New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mainpage sections are not shown as children in the treeview (Origin: bugzilla #684781) #4899

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.2-SVN on platform Other
Assigned to: Dimitri van Heesch

On 2012-09-25 13:12:17 +0000, Philipp Moeller wrote:

Considering

/*!
\mainpage Mainpage

\section intro Introduction
Text
\section more More Info
More Text
*/

and

/*!
\page my_page A Page

\section page_intro Introduction
Text
\section page_more More Info
More Text
*/

and a default doxygen configuration with GENERATE_TREEVIEW = YES,
DISABLE_INDEX = YES the two section of the mainpage are not added as
children to the tree while the children of the normal page are.

The expected outcome is for the mainpage and page to behave
in the same way.

On 2012-09-30 08:30:21 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2012-10-01 11:40:10 +0000, Philipp Moeller wrote:

The recent update shows the sections in the treeview, but they are not correctly nested. This is due to checks for Doxygen::mainPage in Line 3306 and Line 3325 in index.cpp, when the mainpage has been given a name. It works fine when the page has been given a name.

Replacing the checks with

if ((hasSections || hasSubPages) && (pd!=Doxygen::mainPage || mainPageHasTitle()))

fixes this.

On 2012-10-07 18:13:00 +0000, Dimitri van Heesch wrote:

Confirmed. I'll include your fix in the next subversion update.

On 2012-12-03 15:01:06 +0000, Philipp Moeller wrote:

Fixed now.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment