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

opening a configfile after another can mix settings (Origin: bugzilla #606084) #3619

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 doxywizard for ---
Reported in version 1.6.2 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2010-01-05 08:32:18 +0000, Roland Fischer wrote:

If opening a configfile with a parameter set and then opening a configfile with this setting blank, it's not cleared and running doxygen uses mixed settings.

In the attached example

  1. open doxyfile1: HTML_HEADER and HTML_FOOTER should be blank
  2. open doxyfile2: HTML_HEADER and HTML_FOOTER should have values
  3. open doxyfile1: HTML_HEADER and HTML_FOOTER still have values even if not in the configfile

saving the configfile (i.e. after changes) the not cleard params are saved as well corrupting the configfile.
This effect you can see on some but not all settings.

Occurence?
always

On 2010-01-05 08:33:30 +0000, Roland Fischer wrote:

Created attachment 150820
Archive containing the 2 example configfiles

On 2010-02-06 16:27:42 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-02-21 12:57:37 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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

@doxygen doxygen added the doxywizard label Jul 19, 2018

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