Bug?: #Include "..." not shown as a HTML link

"Edgar 't Hart" <[email protected]>
Newsgroups gmane.text.doxygen.devel
Message-ID <[email protected]>
Hi,
I am creating some documentation of our sources, with the
SOURCE_BROWSER setting set to TRUE, I see a correct HTML link in my
"CTestExtra Class Reference" to the .h file in which it was declared.
When clicking this link, it jumps to my 'TestExtra.h' page, fromwhich
I can jump to 'Go to the documentation of this file.' the 'TestExtra.h
File Reference' page.

But I do not want SOURCE_BROWSER enabled, because I dont want our .h
files to be in the documentation. I have set VERBATIM_ HEADERS to
FALSE.
I do have enabled the SHOW_INCLUDE_FILES.
When I now open my 'CTestExtra Class Reference' the
#include <TestExtra.h>
but it is not shown as a link.

I have traced the problem to:
Doxygen.cpp - line 769:
      if ( fd->generateSourceFile()) // generate code for header
      {
        cd->setIncludeFile(fd,iName,local,!root->includeName.isEmpty());
      }
      else // put #include in the class documentation without link
      {
        cd->setIncludeFile(0,iName,local,TRUE);
      }


Can I let the "CTestExtra Class Reference" page's #include
"TestExtra.h" make it jump directly to 'TestExtra.h File Reference'

The link at the bottom of the class reference page does seem to work correctly
When looking at classdef.cpp - line 992:
        if (fd->generateSourceFile())
        {
          ol.writeObjectLink(0,fd->getSourceFileBase(),0,fname);
        }
        else if (fd->isLinkable())
        {
          ol.writeObjectLink(fd->getReference(),fd->getOutputFileBase(),0,
              fname);
        }
        else
        {
          ol.docify(fname);
        }

I see there are three possibilites, 1:link_to_code_file,
2:link_to_file_reference(the one I also want), 3:plain_text

Could some help me solve this ?

Regards,
Edgar

------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.