Skip to content
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 in C++ classes gets mixed with PyROOT doc box #8712

Closed
etejedor opened this issue Jul 22, 2021 · 3 comments
Closed

Documentation in C++ classes gets mixed with PyROOT doc box #8712

etejedor opened this issue Jul 22, 2021 · 3 comments

Comments

@etejedor
Copy link
Contributor

The box that contains PyROOT documentation for a given class used to appear after the documentation that is written in the C++ file for that class. This is not the case anymore, for example:

https://root.cern.ch/doc/master/classTTree.html
https://root.cern.ch/doc/master/classTFile.html

Currently the first sentence of the C++ file docs appears first, after that there is the PyROOT box and finally the rest of the docs present in the C++ file.

@couet
Copy link
Member

couet commented Jul 23, 2021

I am investigating why the Python panels are now coming first in the documentation. I think they came last just "by chance" before. Nothing indicates which \class TFile should be read first. Which by the way is something also a bit stange ie: twice the same \class ... I suspect Doxygen behavior is undefined in that case. I did not find anything mentionning the fact we can have the same \class twice... I am investigating ... no solution yet.

@couet
Copy link
Member

couet commented Jul 27, 2021

I opened an issue on the doxygen repository asking what the behaviour should be when \class is defined twice.
doxygen/doxygen#8693

@etejedor
Copy link
Contributor Author

This was fixed by #8971

@etejedor etejedor added this to Issues in Fixed in: not applicable via automation Sep 27, 2021
@etejedor etejedor added this to Issues in Fixed in 6.26/00 via automation Sep 27, 2021
@etejedor etejedor removed this from Issues in Fixed in: not applicable Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants