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

MAX_DOT_GRAPH_DEPTH (Origin: bugzilla #592626) #3487

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 minor in component documentation for ---
Reported in version 1.6.0 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-08-21 20:47:06 +0000, Bob Fletcher wrote:

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.

On 2013-04-19 18:31:33 +0000, albert wrote:

Created attachment 241946
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.

On 2013-04-19 20:06:48 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2013-05-19 12:36:50 +0000, Dimitri van Heesch wrote:

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.

@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