| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / / / |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Default doxygen search mechanism doesn't work when using with XHTML output
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The problem has been tested with the doxygen test 021. With the output format html all works OK.
- When giving a `t` in the search window a window appears with the message "This XML file does not appear to have any style information associated with it. The document tree is shown below."
- the `<html> statement has to replaced by `<html xmlns="http://www.w3.org/1999/xhtml">` in searchindex.cpp (is normally also present in the non search xhtml files).
- this results in a window with just the words:
Loading....
Searching...
No Matches
- this is due to the extra `<!--` / `-->` in the htmlsearchresults.tpl (strange enough html output has no problem with it).
- When giving a `a` in the search windows we get a "File not found" message as the file nomatches.html cannot be found
- the extension for "nomatches" has to be set properly as well (search.js), for the other files this is done a few lines upward.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
- Change TooltipManager back into a singleton
- Give the OutputList object a unique output id
- Increment the id at each startFile() atomically
- Pass the id to the HTML code generator
- Store tooltips per output id.
- Keep track of tooltips that are already written for a given id
- for output formats other than HTML the output id is 0 and tooltips are
not collected and written
|
|\ \ \
| | | |
| | | | |
Exclude markdown mapped documentation files from Files list
|
| | |/
| |/|
| | |
| | |
| | | |
The files with an obvious documentation extension are excluded from the "Files list" (e.g in top blue bar).
Files that are mapped through `EXTENSION_MAPPING` to markdown files are also documentation files and should also be excluded.
|
|\ \ \
| | | |
| | | | |
Making the use of DOT_CLEANUP more transparent
|
| |/ /
| | |
| | |
| | |
| | | |
- The setting `DOT_CLEANUP` is not only used for `dot` files but also for temporary `msc` and `plantuml` files, though this was not clear from the documentation.
- For the docbook output format the removal of the `dot` and `msc` files was not don like in the output formats html / LatTeX / rtf.
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
- Removing the `txt` and `doc` extension from the default list of `FILE_PATTERNS
- Updating documentation
- Incorrect parsing for the doxywizard of some \ref items (i.e. when the description contains a space, made compatible again with that happens in configgen.py).
|
| | |
|
| |
| |
| |
| |
| |
| | |
- Further fixes to make classes inside inline namespaces appear in the
parent scope again.
- Also added a test case to check for regression
|
| | |
|
|\ \
| | |
| | | |
XHTML: div tag not possible as part of a p tag.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With test 76 we get a number of messages like:
```
element p: validity error : Element div is not declared in p list of possible children
```
this is a regression on issue #8169 / pull request #8170.
The `<div>` tag is not allowed as child of a `<p>` tag and furthermore in the output when a number of items should be on one line this is not the case anymore.
This all can be corrected by means of using the `<span>` tag instead of the `<div>` tag.
|
|\ \ \
| | | |
| | | | |
issue #8186 Path resolving breaks on included @ sign
|
| | | |
| | | |
| | | |
| | | | |
Add in the `@` sign as possible character in a FILEMASK
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Should also ignore `\r` as white space
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having a doxygen configuration file like:
```
QUIET=YES
@INPUT = file
@UNKNOWN =
@UNKNOWN1
@UNKNOWN 1
@UNK # test
```
we get the warnings
```
warning: ignoring unsupported tag 'UNKNOWN' at line 3, file Doxyfile
warning: ignoring unknown tag 'UNKNOWN1' at line 4, file Doxyfile
warning: ignoring unknown tag 'UNKNOWN' at line 5, file Doxyfile
warning: ignoring unknown tag '1' at line 5, file Doxyfile
warning: ignoring unknown tag 'UNK' at line 6, file Doxyfile
# Difference with default Doxyfile 1.9.0 (fa65bb38f81457d00f9c900bb57eb68bea59b1b4)
QUIET = YES
INPUT = file
```
especially the missing of a warning about the `@` in `@INPUT` can be a bit misleading (it might be that the user wanted to use `@INCLUDE` and and specified `@INPUT`
It would be better to have a warning about a not handled character instead of just ignoring it.
|
| | | |
|
|/ / |
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
Unclear description of QHG_LOCATION
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The description of `QHG_LOCATION` is a bit unclear (compare with `HHC_LOCATION`).
(based on https://stackoverflow.com/questions/64795335/qhelpgenerator-with-doxygen-keep-showing-sh-1-permission-denied/64801829#64801829)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
issue #8169 "\emoji heavy_check_mark" produces ✓ instead of ✔️
|
| |/ /
| | |
| | |
| | | |
Create the possibility to change the used font for an emoji (the default is unchanged, but an example is given of how it is used at the site: https://unicode.org/emoji/charts/full-emoji-list.html).
|
| | | |
|
|\ \ \
| |/ / |
|
| |\ \
| | | |
| | | | |
Doxygen crashes on Fortran
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having a Fortran file like:
```
!> module docu
MODULE test_mod
INTERFACE
!> @brief iets
SUBROUTINE subr_i(this)
INTEGER this
END SUBROUTINE subr_i
END INTERFACE
!< @brief type brief
TYPE, PUBLIC :: test_type
!> docu
integer i
END TYPE test_type
END MODULE test_mod
```
this is due to the fact that a incorrect start of comment `!<` is used for the `TYPE` and that initiated because the last `SUBROUTINE` argument does not have any documentation.
The actual cause is that at the end of a subroutine the `vtype` is not properly reset.
|
| | | |
| | | |
| | | |
| | | | |
Typo in namespacedef.h as found by Fossies
|
|/ / / |
|
|/ /
| |
| |
| |
| |
| | |
Split Definition/ClassDef/NamespaceDef/MemberDef into a immutable and mutable part
Aliases are immutable, other symbols are stored using an immutable
interface but can be made mutable explicitly by dynamic casting.
|
|\ \
| | |
| | | |
Incorrect handling of string with spaces and no quotes
|
| | |
| | |
| | |
| | | |
Correcting some (Cygwin) compilation warnings / errors
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
During some tests on the documentation of LLVM the (CMake generated) doxygen configuration file contained the line:
```
DOT_PATH=D:\Program Files (x86)\Graphviz2.38\bin\dot.exe
```
and this was interpreted by doxygen as
```
DOT_PATH = D:\ProgramFiles(x86)\Graphviz2.38\bin\dot.exe
```
without any message other than that later on the `dot` executable could not be found.
It is clear that here the double quotes were missing.
This problem has been solved by giving a warning and setting the value to the default value.
- configimpl.l
- config_doxyw.l
during the checking some debug facilities for the doxywizard were required and this has been implemented:
- config_doxyw.l
- doxywizard.h
- doxywizard.cpp
it was also discovered that in case of none existing int or bool values were specified the wrong "defaults" were taken (it was set to `0` / `false`), now the correct defaults are taken
- inputbool.cpp
- inputint.cpp
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
DGA45-Rel_1_8_20_DGA
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | | |
Fix ANSI-C anonymous (unnamed) struct/unions duplicated names issue
|