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 592626 - MAX_DOT_GRAPH_DEPTH
MAX_DOT_GRAPH_DEPTH
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.6.0
Other Windows
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-08-21 20:47 UTC by Bob Fletcher
Modified: 2013-05-19 12:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
PATCH: correct distance counting in callre graphs (2.72 KB, patch)
2013-04-19 18:31 UTC, albert 		none Details | Review

Description Bob Fletcher 2009-08-21 20:47:06 UTC 
It appears to me that the MAX_DOT_GRAPH_DEPTH is off by 1. For example, if I set it to 1, the collaboration diagram shows no edges; if I set it to 2, it shows 1 level of edges; etc. 
This seems inconsistent with comments in latest Doxyfile. Perhaps I don't understand what is meant by edges. I assume they are the same as paths or arcs.
Comment 1 albert 2013-04-19 18:31:33 UTC 
Created attachment 241946 [details] [review]
PATCH: correct distance counting in callre graphs

When generating a graph with MAX_DOT_GRAPH_DEPTH set to 1 only the nod itself is shown, with MAX_DOT_GRAPH_DEPTH set to 2 only the node plus its neighbors, so indeed not the edges/ connections are counted but the nodes.

This patch corrects this problem. When MAX_DOT_GRAPH_DEPTH is set to 1 the node itself plus the neighbor nodes are shown.
In case MAX_DOT_GRAPH_DEPTH is set to 0 the entire graph is still shown.

the variable m_maxDistance was not used and has been removed.
Comment 2 Dimitri van Heesch 2013-04-19 20:06:48 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2013-05-19 12:36:50 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.