After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 742445 - Wrong icons in TOC of CHM help
Wrong icons in TOC of CHM help
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.9.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-01-06 10:24 UTC by Eugene
Modified: 2015-06-27 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example of TOC with wrong icons (7.98 KB, image/png)
2015-01-06 10:24 UTC, Eugene 		Details
Sources used for CHM generation (3.14 KB, application/octet-stream)
2015-01-06 10:25 UTC, Eugene 		Details

Description Eugene 2015-01-06 10:24:10 UTC 
Created attachment 293909 [details]
Example of TOC with wrong icons

Some icons in a table of contents of CHM help became wrong. Specifically, those icons which represent @page, @section, @subsection and @subsubsection commands.

"Leaves" in a TOC tree (entries which has no nested entries) must have "page" icon, while other nodes (entries with nested entries) must have "book" icon. Now it is not so.

I attach screenshot of TOC (where I've marked correct and wrong icons) and source which was used for its generation.

This got broken since version 1.8.0; last "good" version with correct icons was 1.7.6.1. And CHM help of Doxygen itself also has this problem, starting from version 1.8.1 (seems it is made by Doxygen too).
Comment 1 Eugene 2015-01-06 10:25:58 UTC 
Created attachment 293910 [details]
Sources used for CHM generation
Comment 2 albert 2015-01-06 20:06:14 UTC 
I've just pushed a proposed patch to github (pull request 286).
Comment 3 Dimitri van Heesch 2015-01-23 19:10:00 UTC 
Thanks, I've merged the pull request
Comment 4 Dimitri van Heesch 2015-06-27 19:01:38 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.10. 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 (preferably in the form of a self-contained example).