| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
PDF generation stops when image with caption is included in a table.
|
| |
| |
| |
| |
| | |
- patch should only be applied to images.
- added doxyfigcaption to manual.sty for completeness, when in future a table with an image and caption might appear in the documentation.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case an image is included in a table and this image has a caption the generation of a PDF stops with the message:
! Misplaced \noalign.
\caption ->\noalign
\bgroup \@ifnextchar [{\egroup \LT@c@ption \@firstofone ...
l.45 \end{longtabu}
This problem has in general been described in: http://tex.stackexchange.com/questions/85919/adding-a-caption-to-a-graphic-inside-a-longtable
In this patch the suggestion from this reference is implemented by defining \doxyfigcaption and using this where a caption is required.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
In the documentation generated by doxygen the table of contents does not start with page number i but with iii, by setting the pagenumbering}{roman} after the clearemptydoublepage titlepage this is corrected. In the beginning of the documentation we set the page numbering to "alph" so it won't interfere with the numbers in the table of contents and the real documentation.
For the doxygen manual similar reasoning is true, furthermore the table of contents was on the left side page (when printed double sided), yhis is corrected as well.
|
| |
| |
| |
| | |
improve performance
|
|/
|
|
| |
documented
|
|
|
|
| |
Implemented caption possibility in RTF documentation for the different image formats, including some streamlining of the code.
|
|\
| |
| | |
Bug 700381 - error state 21 with fortran code (fixed format)
|
| |
| |
| |
| | |
Problem is caused by similar quotes inside quotes, in Fortran it is possible to "escape" quotes by doubling them.
|
|/
|
|
|
| |
This patch fixes a problem on Linux where in a number of cases doxygen crashed when an unnamed interface existed and the routine itself was in the same source file.
Furthermore the end line of routines is set correctly so inline source code in Fortran will be possible as well.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Don't overwrite the protection settings in current entry, they may result from a comment block
|
| |\
| | |
| | | |
Bug 732356 - doxygen's \param command is confused by some python default values
|
| | |
| | |
| | |
| | | |
Decrement brace count only in case of a ')' not in case of a ','
|
| |\ \
| | | |
| | | | |
Bug 361814 - python: tuple assignment not recognized as variable initialization
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
added possibility for the separate variables from a tuple assignment:
a,b,c =
and
(a,b,c) =
|
| |\ \
| | | |
| | | | |
Bug 641036 - python script with #!/usr/bin/python are not documented correctly
|
| | |/
| | |
| | |
| | | |
Handle #! at first line as a special comment (on *nix systems starts the mentioned program with the file as input)
|
| | |
| | |
| | |
| | | |
function (C++)
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_593642
|
| |/
| |
| |
| | |
In case STRIP_CODE_COMMENTS is set the doxygen specific comment is stripped from the output.
|
|\ \
| | |
| | | |
Bug 578720 - [Python] Add pyw as a valid extension
|
| |/
| |
| |
| | |
Added pyw as extension, based also on: https://docs.python.org/2/tutorial/appendix.html (15.1.2. Executable Python Scripts)
|
|\ \
| | |
| | | |
Bug 735152 - Python: Allow undocumented "cls" parameter for class methods
|
| |/
| |
| |
| | |
Made 'cls' parameter analogous to the 'self' parameter. See also https://www.python.org/dev/peps/pep-0008 (paragraph: Function and method arguments)
|
|/ |
|
| |
|
| |
|
|
|
|
| |
parameters
|
| |
|
| |
|
|
|
|
| |
a warning
|
| |
|
|\
| |
| | |
Correct / set types for python variables
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The bool python type was not handled.
In case of the initialization by means of a method call a variables was was aid to be a tuple (e.g. env= os.environ.copy())
Methods with initialization with defaults were shown without arguments in the brief description (e.g. def create_dir(dir, create=True):)
Arguments with values in method calls were seen as variables variables in case of continuation lines (e.g.
parser.add_argument("--https_proxy", nargs="?", help="Proxy to be used for https requests",
action="store", const="myproxy.domain.com:8080")
in this case action was seen as variable).
|
|\ \ |
|
| |\ \
| | |/
| |/| |
Add WARN_AS_ERROR option to stop execution at first warning (equivalent of compilers' -Werror option)
|
| | |
| | |
| | |
| | | |
compilers' -Werror option)
|
| | |\
| | | |
| | | | |
Markdown with @cond and @endcond
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
|
| | |\ \
| | | | |
| | | | | |
Fortran module private variables and EXTRACT_PRIVATE = NO
|