| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Added cross reference link that was missing
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the new commands \hidecallgraph and \hidecallergraph it is possible to suppress a call or caller graph even though the corresponding option CALL_GRAPH or CALLER_GRAPH is set.
commands.doc
config.xml
diagrams.doc
- updating documentation to support new commands
entry.cpp
- initialize callgraph and callergraph with the value from the config file
commentscan.l
- add handling for the new commands
context.cpp
memberdef.cpp
util.cpp
- getting the option for CALL_GRAPH and CALLER_GRAPH is not necessary anymore as it is incorporated in the initialization of an Entry item
dbusxmlscanner.cpp
- initialization is done in the Entry item
vhdljjparser.cpp
- gBlock was a static variable and therefore initialized before the doxygen main routine started. A Entry element sets now the default for callgraph and callergraph based on the config file and as the config file is not yet known at that moment the value for CALL_GRAPH and CALLER_GRAPH were set to False. By making a pointer of gBlock and doing an appropriate new Entry call this problem is overcome.
|
|/ |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Adjusted text to better reflect current situation.
|
|\ \
| |/ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adjusts some problems regarding image sizes in LaTeX output of doxygen (a.o. Bug 738299 - When using msc or PlantUML, the default latex for the created image should include [width=\linewidth]) this has been done is such a way that all the "image" commands (i.e. image, dot, dotfile, msc, mscfile, diafile, startuml) operate in a similar way / have the same possibilities.
- commands.doc
Adjusted documentation to reflect changes.
- cmdmapper.cpp
- cmdmapper.h
Added utility function to map command id back to command name
- doctokenizer.h
- doctokenizer.l
Handle Caption and Size indication. Required also that some other rules had to be tightened a bit (like usage of {} in startuml and usage of "" for captions. This was already described in the documentation in this way).
- docparser.cpp
- docparser.h
Created routine to uniformly handle the Caption and size indications and store them in a general way.
- latexgen.cpp
Replaced graphicx package by adjustbox package (includes graphicx) to support "min width" etc.
- doxygen.sty templates\latex
Added commands to make commands with and without caption behave similar.
- docbookvisitor.cpp
- docbookvisitor.h
- htmldocvisitor.cpp
- latexdocvisitor.cpp
- latexdocvisitor.h
- printdocvisitor.h
- xmldocvisitor.cpp
Created routine to uniformly handle the Caption and size indications in a general way.
- indexpage.xml (testing\022)
- indexpage.xml (testing\031)
- class_receiver.xml (testing\037)
- class_sender.xml (testing\037)
Adjusted example output.
|
|\ \
| |/ |
|
| |\
| | |
| | | |
Create an easy possibility to take a snippet from the current file.
|
| | |
| | |
| | |
| | |
| | |
| | | |
In case the snippet of code is in the current file one has to specify the name of the file and also see to it that the file is reachable through the EXAMPLE_PATH.
A use case is the case of a list of initial values here it is quite often more convenient to have the values listed in a 'nice' list than direct in the definition line.
With this patch it is possible to specify the name of the file where the snippet resides as: this
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | | |
not available
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
In regular use it happens that it is more convenient to have multiple extra HTML stylesheets, e.g. in case of different levels of requirements: company, department, project
With this patch it is possible to specify multiple HTML stylesheets.
Note: for compatibility the configuration parameter HTML_EXTRA_STYLESHEET has not been renamed to HTM_EXTRA_STYLESHEETS.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/ |
|
| |\
| | |
| | | |
Bug 625601 - FORTRAN: recognition free versus fixed formatted code
|
| | |
| | |
| | |
| | | |
Correction in documentation based on comment by dnm on June 19 2014
|
| |/
| |
| |
| |
| |
| |
| | |
in filenames
Adjusted the rules files and where and the vcproj file so it can handle paths with spaces as well.
When generating the documentation (Cygwin) a small problem appeared in a Makefile when there is a space in the path, this is solved as well.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Open() replaced by xopen() that internally uses the encoding argument
only for Python 3. The earlier usage of the codecs module and of the
prefixed unicode string literals was removed.
- Some lists of prototypes were sorted to get the same translator report
for different versions of Python.
- The local dedent() definition was replaced by textwrap.dedent().
(The older versions of Python did not have the module.)
- Tested on Windows for Python 2.6.0, 2.7.7, 3.0.1, and 3.4.1.
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
Added documentation for H4, H5 and H6 command to be complete and extended IMG description a bit
|
|
|
|
| |
This concerns the BODY and MULTICOL tags.
|
| |
|
|
|
|
| |
Currently the FAQs are in a numbered list, no index / overview. This patch places the FAQs in paragraphs resulting in a readable overview (in index or with a tableofcontents in HTML
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The word LaTeX was used as just the word and on other places as \f$\mbox{\LaTeX}\f$
This has been made more consistent by means of the definition of the Alia \LaTeX (similar for \TeX)
Some names of executables etc. were not set in a 'code' font.
|
| |
|
| |
|
| |
|
|
|
|
| |
Removed superfluous < sign
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_625601
|
| |
| |
| |
| |
| | |
The recognition of the type (free or fixed) of Fortran code is not reliable possible. A well known possibility as used with compilers as well is to specify the type of code by means of the extension.
With EXTENSION_MAPPING it is possible to select the type of Fortran code, when not explicitly set doxygen tries to guess the type of Fortran code.
|
|/
|
|
| |
This patch describes an alternative way to get rules / debug information from flex files
|
|\
| |
| | |
Made documentation more consistent
|
| |
| |
| |
| | |
Made documentation for custom commands more consistent and remove not required backslashes
|