-
-
Notifications
You must be signed in to change notification settings - Fork 686
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
Documentation warnings about large graphs #5184
Comments
Increasing Is there any chance you could produce a patch (or patch set) which applies the suggestions? If you are still having trouble creating a PR, zipping up the patch (set) and sharing it in a comment would work. |
Indeed I've been a bit busy and I still have problems with creating a PR, for a number of issues it would be possible for me to generate a patch (Unix diff format that can be applied with the patch command) and provide it as a comment in a zip file. There are a number of issues though where there is first some advise necessary (like you have given here in the comment #5184 (comment)). I'll see what I can do. |
Proposed patch: diff.patch |
This should prevent warnings about large graphs. Closes InsightSoftwareConsortium#5184.
Description
When creating the documentation (locally, as I don't see them on cdash, https://open.cdash.org/viewBuildError.php?type=1&buildid=10169225, might be that I'm missing there something) we get the warnings:
Expected information
No warning
Actual information
See Description
Versions
Current master: acaddf4
Additional Information
There are the solutions
DOT_GRAPH_MAX_NODES
\hideincludedbygraph
see https://www.doxygen.nl/manual/commands.html#cmdhideincludedbygraph\hideinheritancegraph
see https://www.doxygen.nl/manual/commands.html#cmdhideinheritancegraphFor a full list of the available commands and their documentation see https://www.doxygen.nl/manual/commands.html
For a full list of commands and the doxygen version in which they are introduced see https://doxygen.github.io/doxygen-docs/da/de1/pg_cmds.html
The text was updated successfully, but these errors were encountered: