| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| | |
= NO
the enabling of the caller graph was set by the references relation (regression on issue #6562)
|
| |\
| | |
| | | |
issue #6764 Incorrect parsing of C enum comments defined using a macro
|
| | |
| | |
| | |
| | | |
When in a `/*` comment skip till end of the comment so a `,` won't be seen as the argument separator.
|
| |\ \
| | | |
| | | | |
issue #6775 LaTex package newunicodechar: "package won't work "
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Some older distributions with newunicode package 1.1 need this option `\usepackage[utf8]{inputenc}`.
Option was already present in the main LaTeX output i.e. refman.tex
|
| |\ \ \
| | | | |
| | | | | |
Bug 645910 - Segfault on recursion while parsing "\subpage A" in "\page A"
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In version 1.7.3 (till 1.8.7) the problem of direct recursion (i.e. in a page is a subpage to itself) we got a segmentation fault, as of 1.8.8 the problem went into an endless loop.
The direct recursion is now detected.
|
| |\ \ \ \
| | | | | |
| | | | | | |
Multiple use of HTML attributes
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case an attribute is used multiple times the XHTML validator gives (here for the style attribute):
parser error : Attribute style redefined
Created routine to merge these types of attributes.
|
| |\ \ \ \
| | | | | |
| | | | | | |
Possibility to show converted fixed form
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create an easy possibility to show the Fortran source as converted from fixed form to free form.
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
secreflist command output shows in 1 column (HTML)
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The output from the `\secref` command shows in 1 column instead of 3.
The `column-count` (also possibile without `-moz` or `-webkit`) should be with the `<ul>` tag instead of the `<div>` tag
|
|/ / / / / |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_lineno_split_examples
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With the commands like `\skip`, `\skipline` it is possible to show parts of a file for further explanation / tutorials. They can be started with `\include` or `\dontinclude` but in case `\include` specifies that the line numbers have to be shown they are only shown in the full example and not in the split up example
- show line numbers in split up example in case `lineno` is required
- add `lineno` option to `\dontinclude` so here also line numbers can be shown.
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_warn_nofile_incl
|
| | | | |
| | | | |
| | | | |
| | | | | |
Create a warning in case no `\include` or `\dontinclude` command has been given before using `\skip`, `\line`, `\skipline` or `\utnil`
|
|/ / / /
| | | |
| | | |
| | | | |
This reverts commit d4243bc66fc911012c8222514d5b33a222993ae5.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
albert-github/feature/bug_abstract_intf_regression_2
Regression on Definition and derived classes that are abstract interfaces (2)
|
| | | | |
| | | | |
| | | | |
| | | | | |
Looks like some more possible problematic places (no test case present)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There was a incorrect cast which didn't show with compilers on *nix, but does on windows.
Problem occurred at least with test 58, 62 and with documentation (tclexample)
|
|\ \ \ \ \
| |/ / / / |
|
| |\ \ \ \
| | | | | |
| | | | | | |
issue #6847 Physical newlines (^^) in ALIASES produce a mismatch between documentation and source code
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
documentation and source code
In 1.8.15 the `^^` was already translated to `\_linebr` but here there was a ` ` (space) after the `^^`, here this is not the case resulting in "warning: Found unknown command `\_linebrline'"
placing a ` ` after the translated value solves this problem.
|
|/ / / / |
|
|\ \ \ \
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
Section title runs into margin
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the PDF version of the doxygen manual we see that for the `\image` command the chapter title the text runs into the margin (due to an unbreakable part).
With this fix the problem is solved.
(see also: https://tex.stackexchange.com/questions/474055/section-title-running-into-margin and , for the ifstar part, https://tex.stackexchange.com/questions/376375/using-ifstar-to-define-a-star-variant)
|
| |\ \ \ \
| | | | | |
| | | | | | |
Remove some doxygen warnings in internal documentation
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Generating the doxygen internal documentation gave some warning messages, these have been corrected.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Latex code double minus goes to endash
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In case in code 2 consecutive minus signs are present they are shown as endash.
using the same code as in the non code part solves the issue.
Issue can e.g. be seen in cpp source code (with e.g. i--) and in the doxygen documentation in the paragraph "Comment blocks in VHDL"
This is a regression in 1.8.15
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
The `...` argument was not documented in case of inline parameter documentation, with `\param` it was possible to document the `...` argument.
|
| |\ \ \ \
| | | | | |
| | | | | | |
issue #6840 Hash character in Markdown code span not rendered correctly
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
A hash sign has a special meaning, so it should be escaped in a code span.
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
A hash sign has a special meaning, so it should be escaped in a code span.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bug 399222 - SORT_BRIEF_DOCS produces wrong results
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Grouped brief (with `\{ ..\}` descriptions were not sorted when `SORT_BRIEF_DOCS` was set, the detailed documentation was sorted already.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Incorrect layout of class index (HTML)
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Regression of #6663
When looking at the example of #4935 the sorting and layout is correct in 1.8.14 but the layout is incorrect in 1.8.15.
The incorrect layout is due to #6663 where a special case was solved for XHTML, the correct procedure should have been that in case of a table row without cells a dummy cell is added.
The changes from #6663 have been reverted and the fix has been corrected (the special case occurred in the doxygen diagrams example).
|
|\ \ \ \ \ |
|