New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VHDL: Bad HTML formatting when using inline sources (Origin: bugzilla #702066) #5209

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-06-12 09:52:05 +0000, lahmson@fantasymail.de wrote:

When the .ini parameter INLINE_SOURCES is set to YES, the HTML format of the architecture reference gets corrupted.
I looked into the HTML file and noticed that after every source code block, an additional is inserted in the HTML code that causes every following member (usually processes) to belong to a hierarchically higher div. Simply deleting these results in a correct formatting.
In the screenshot you can see 3 process descriptions and the wrong placement of the second and third one. They are aligned correctly when I disable inline sources.

On 2013-06-12 09:53:14 +0000, lahmson@fantasymail.de wrote:

Created attachment 246598
wrong format due to inline sources

On 2013-06-12 09:57:50 +0000, lahmson@fantasymail.de wrote:

Created attachment 246599
VHDL test source file

I used this file to create the doxygen output.

On 2013-06-16 07:40:57 +0000, mk wrote:

Created attachment 246925
fixed the and the source comment bug

On 2013-06-16 08:08:27 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next GIT update.

On 2013-08-23 15:04:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment