Some methods, such as wfProfileIn(), wfProfileOut() don't really add much to a lot of the call graphs, and end up making them a lot more complex
Being able to exclude methods from being drawn would be really useful
Version: unspecified
Severity: enhancement
Maybe http://www.stack.nl/~dimitri/doxygen/config.html#cfg_exclude_symbols can be used for this.
Should probably be reported upstream. There are commands to enable the graphs on a per function basis \callgraph \callergraph . Maybe two new commands could be added to explicitly disable them such as \nocallgraph & \nocallergraph ?
Is this still a problem? maintenance/Doxyfile now specifies CALL_GRAPH = NO and CALLER_GRAPH = NO.
Reedy: Is this still a problem?
maintenance/Doxyfile now specifies CALL_GRAPH = NO and CALLER_GRAPH = NO.
Yes, well, sort of.
The call graphs have some use, but there are numerous methods that we don't really care if they are called - it gives no information.
They were turned off because they were too big etc
Revisiting a decade old bug.
We had to:
CALL_GRAPH = NO CALLER_GRAPH = NO
Looking at the Doxygen configuration https://www.doxygen.nl/manual/config.html , some methods can have their call or caller graphs generated using \callgraph or \callergraph.
And if we were to turn the options to YES again, methods can be opted out with \hidecallgraph and \hidecallergraph.
Those got added by https://github.com/doxygen/doxygen/pull/302 and released with Doxygen 1.8.10 (June 2015).
So essentially this task is fixed, upstream provided a way to hide some methods. I guess we can have a task to figure out whether we want to enable the call/caller graphs again and then hide some of the too generous ones. Else just mark this as resolved :)