doxygen-users — List for users of doxygen

Re: [Doxygen-users] Doxygen-1.2.11 in CVS

[Luigi B. <bal...@ma...>]

Hi,
	I don't know if I just didn't notice it until now.
In my project, I'm having Doxygen run through a few .docs files beside my 
sources. Such files contain general documentation pages. They do not 
contain any \file command, just a long \page each.
I just ran Doxygen 1.2.11, and all of a sudden they appear into the 
generated file index. However, they are not documented, so that their 
entries don't link to anywhere---and in the latex version they appear with 
a ?? page number.

Any insight?

Thanks,
	Luigi

Re: [Doxygen-users] Doxygen-1.2.11 in CVS

[Luigi B. <bal...@ma...>]

Hi,
	the attached file causes a strange parsing warning when used with a 
freshly generated doxyfile. The comments in the file explain the issue.

Bye,
	Luigi

RE: [Doxygen-users] Buffer Overflow

[Stephen M. <mor...@no...>]

I would say it would be from an autogenerated file, there are 100s of them
in the source tree.  Is there a config option or something I can do as a
work around?  Alternatively for the future, is it possible for Doxygen to
just ignore errors of these type and keep processing rather than throwing a
fatal?

Regards

Stephen


-----Original Message-----
From: Dimitri van Heesch [mailto:di...@st...]
Sent: Saturday, September 29, 2001 5:38 AM
To: dox...@li...
Subject: Re: [Doxygen-users] Buffer Overflow


On Fri, Sep 28, 2001 at 05:13:26AM +0800, Stephen Morrison wrote:
> Hi,
> 
> I am getting this error in 1.2.10:
> 
> "input buffer overflow, can't enlarge buffer because scanner uses REJECT"
> when the tool is parsing a file.  Is this just a running out of memory
> issue?

See FAQ #12. If you have an example that produces this for another reason, 
please send it.

Regards,
  Dimitri

_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Re: can't find doxfont

[Jesper B. <jb...@me...>]

On Monday 01 October 2001 22:18, you wrote:
> >I have a small problem with getting doxygen to cooperate with the
> >graphviz tool. In all its simplicity the problem is that when I run
> >doxygen, I get the message
> >   can't find font doxfont in .
> >from dot.  The graphs are still generated, but the font used in place of
>
> the
>
> >missing doxfont  is too large, so that labels wont fit in the enclosing
>
> box.
>
> I have seen this on Windows. It was a while ago, but as I recall I fixed it
> by copying doxfont.ttf to the directory where dot is run from. Or perhaps I
> had to put it on the path? I think the problem is that the command to dot
> (performed by doxygen) is fully specifying the path to the .dot files, and
> the "current directory", for dot, is not what you are expecting.
>
> Hope this helps,
>
> Don McClimans
>

Unfortunately that is not it. - The problem you had on windows was that 
doxygen provided an incorrect fontpath to dot. - In this case the path is
correct -- as seen by that the error message from dot explicitly says
that it is looking in the current directory for the doxfont -- and  I have 
verified that the doxfont.ttf is actually created in that directory, so the 
real question is why dot wont use the file. 
It might be that dot now expects an index file of all fontfiles in that 
directory or something similar. Of course I can figure that out by reading 
the source, but being lazy, I hope that there are someone around  
that has already solved the problem.

-- 

Jesper Bojesen
Email: 	jb...@me...
Phone:	(+45) 40 99 55 03

[Doxygen-users] Re: can't find doxfont

[Don M. <dmc...@in...>]

>I have a small problem with getting doxygen to cooperate with the
>graphviz tool. In all its simplicity the problem is that when I run
>doxygen, I get the message
>   can't find font doxfont in .
>from dot.  The graphs are still generated, but the font used in place of
the
>missing doxfont  is too large, so that labels wont fit in the enclosing
box.

I have seen this on Windows. It was a while ago, but as I recall I fixed it
by copying doxfont.ttf to the directory where dot is run from. Or perhaps I
had to put it on the path? I think the problem is that the command to dot
(performed by doxygen) is fully specifying the path to the .dot files, and
the "current directory", for dot, is not what you are expecting.

Hope this helps,

Don McClimans

[Doxygen-users] EXAMPLE_PATH bug ?

[<vel...@te...>]

when i use
EXAMPLE_PATH           = ..
or
EXAMPLE_PATH           = .
or
EXAMPLE_PATH           = xpm \
                         ..

"Searching for example files..." never stop

bug ?

_______________________________________________________________________

 Vélizar VESSELINOV
 Chef de projet                       Téléphone : +33.(0)4.67.59.30.47
 Pôle Informatique             E-mail : vel...@te...

 Techsia S.A.
 Cap Alpha - Avenue de l'Europe, Clapiers
 34940 Montpellier Cedex 9                      http://www.techsia.com
 France                                     Fax : +33.(0)4.67.59.36.19
_______________________________________________________________________

      Les données maîtrisées        ~         The end of doubt

[Doxygen-users] Bug: doxytag

[<vel...@te...>]

Code HTML :
<li><a class="elRef" doxygen="qt.tag:"
href="qwidget.html#acceptDrops">acceptDrops</a>&amp;nbsp;() const

View with IE6 :
acceptDrops&nbsp;() const
           ^^^^^^ bug ?

XML qt.tag :
    <member kind="function">
      <name>acceptDrop</name>
      <anchor>acceptDrop</anchor>

<arglist>&amp;nbsp;(&amp;nbsp;const&amp;nbsp;QMimeSource&amp;nbsp;*&amp;nbsp
;mime&amp;nbsp;) const</arglist>
    </member>

_______________________________________________________________________

 Vélizar VESSELINOV
 Chef de projet                       Téléphone : +33.(0)4.67.59.30.47
 Pôle Informatique             E-mail : vel...@te...

 Techsia S.A.
 Cap Alpha - Avenue de l'Europe, Clapiers
 34940 Montpellier Cedex 9                      http://www.techsia.com
 France                                     Fax : +33.(0)4.67.59.36.19
_______________________________________________________________________

      Les données maîtrisées        ~         The end of doubt

Re: [Doxygen-users] "can't find doxfont"

[Neil S. <ns...@ci...>]

Spooky timing, I've just posted a message on a similar issue in the thread
"Which version of gviz, and why?", though I don't see the doxfont messages
anywhere.

Neil.


----- Original Message -----
From: "Jesper Bojesen" <jb...@me...>
To: <dox...@li...>
Sent: Monday, October 01, 2001 9:30 AM
Subject: [Doxygen-users] "can't find doxfont"


>
> Hi,
>
> I have a small problem with getting doxygen to cooperate with the
> graphviz tool. In all its simplicity the problem is that when I run
> doxygen, I get the message
>    can't find font doxfont in .
> from dot.  The graphs are still generated, but the font used in place of
the
> missing doxfont  is too large, so that labels wont fit in the enclosing
box.
>
> I have confirmed that the font file doxfont.ttf is generated in the
current
> directory, by commenting the code that deletes it, and the error message
> is printed by dot, so it is clear that dot is found.
>
> Any suggestions to what I can do differently to get this to work will be
most
> welcome.
>
> Version numbers are:
>     doxygen: 1.2.6
>     graphviz: 1.7.7
> all on linux  redhat 7.0.
>
> --
>
> Jesper Bojesen
> Email: jb...@me...
> Phone: (+45) 40 99 55 03
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] "can't find doxfont"

[Jesper B. <jb...@me...>]

Hi,

I have a small problem with getting doxygen to cooperate with the 
graphviz tool. In all its simplicity the problem is that when I run 
doxygen, I get the message 
   can't find font doxfont in . 
from dot.  The graphs are still generated, but the font used in place of the 
missing doxfont  is too large, so that labels wont fit in the enclosing box. 

I have confirmed that the font file doxfont.ttf is generated in the current 
directory, by commenting the code that deletes it, and the error message 
is printed by dot, so it is clear that dot is found. 

Any suggestions to what I can do differently to get this to work will be most
welcome.
 
Version numbers are: 
    doxygen: 1.2.6
    graphviz: 1.7.7
all on linux  redhat 7.0.

-- 

Jesper Bojesen
Email: 	jb...@me...
Phone:	(+45) 40 99 55 03

Re: [Doxygen-users] Which version of gviz, and why?

[Neil S. <ns...@ci...>]

Thanks for the reponse,

Onorio Catenacci suggested...

>Why don't you try 1.7 and let us know what happens?  What's the worst that
>could happen?

Well I decided to try this damn fool crazy idea out :)

Using gviz 1.7c I got diagrams which look much the sames as those produced
by 1.5, except that in many cases the text within the boxes is not
completely contained by the boxes. This doesn't happen with gviz 1.5.  I'm
running on Solaris 2.6 (Sparc) using the standard X server. I assume the
problems are due to font issues; I guess this is an issue for the gviz guys.

Thanks again,

Neil.

----- Original Message -----
From: "Dimitri van Heesch" <di...@st...>
To: <dox...@li...>
Sent: Friday, September 28, 2001 8:35 PM
Subject: Re: [Doxygen-users] Which version of gviz, and why?


> On Fri, Sep 28, 2001 at 03:20:24PM +0100, Neil Salter wrote:
> > Hello,
> >
> > Which version of gviz/dot should I be using with doxygen?
>
> I currently use 1.7.8 myself (on Linux). The docs still
> suggest version 1.5 but that's more because that part hasn't been
> updated :-) Any version after 1.5 will probably work, but I have not much
> control over the development on graphviz, so I cannot guarantee this.
>
> Regards,
>   Dimitri
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Which version of gviz, and why?

[Neil S. <ns...@ci...>]

Thanks for the reponse. 

Onorio Catenacci suggested...



----- Original Message ----- 
From: "Dimitri van Heesch" <di...@st...>
To: <dox...@li...>
Sent: Friday, September 28, 2001 8:35 PM
Subject: Re: [Doxygen-users] Which version of gviz, and why?


> On Fri, Sep 28, 2001 at 03:20:24PM +0100, Neil Salter wrote:
> > Hello,
> > 
> > Which version of gviz/dot should I be using with doxygen?
> 
> I currently use 1.7.8 myself (on Linux). The docs still 
> suggest version 1.5 but that's more because that part hasn't been
> updated :-) Any version after 1.5 will probably work, but I have not much
> control over the development on graphviz, so I cannot guarantee this.
> 
> Regards,
>   Dimitri
> 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] Doxygen-1.2.11 in CVS

[Anthony Y. <an...@ac...>]

	I love the new class collaboration diagrams!  Very useful!
I also like the new layout of the lists (HTML).  Great Job!


-----Original Message-----
From: dox...@li...
[mailto:dox...@li...] On Behalf Of Dimitri
van Heesch
Sent: Sunday, 30 September, 2001 12:47
To: dox...@li...
Subject: [Doxygen-users] Doxygen-1.2.11 in CVS

Hi,

Here is what has changed since last week's update:
-----------------------------------------------------------------------
+ BUG: Fixed crash bug when filtering CR+LF's from input (thanks to Petr
       Prykril).
+ BUG: Fixed generated makefile dependencies for USE_PDFLATEX = YES
       (thanks to Marcus Holland-Moritz)
+ BUG: "\retval #VALUE" now links to VALUE if documented. The same works
       for \exception and \throws
+ BUG: Sorting the alphabetical list was broken for nested classes.
-----------------------------------------------------------------------

Enjoy,
  Dimitri

_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] bad doxygen html output

[Arne S. <ar...@sc...>]

Please see this page which has completely wrong mapping of source code parts 
to the documentation:

http://www.schirmacher.de/tmp/problem/doc/html/classPageEditor.html

The corresponding sources and the kino.dox doxygen input file are in 
http://www.schirmacher.de/tmp/problem/ .

I tried this with v. 1.2.10 and 1.2.11. Please advise how I can get a correct 
output, maybe by omitting options that trigger the bugs.

Arne

[Doxygen-users] Doxygen-1.2.11 in CVS

[Dimitri v. H. <di...@st...>]

Hi,

Here is what has changed since last week's update:
-----------------------------------------------------------------------
+ BUG: Fixed crash bug when filtering CR+LF's from input (thanks to Petr
       Prykril).
+ BUG: Fixed generated makefile dependencies for USE_PDFLATEX = YES
       (thanks to Marcus Holland-Moritz)
+ BUG: "\retval #VALUE" now links to VALUE if documented. The same works
       for \exception and \throws
+ BUG: Sorting the alphabetical list was broken for nested classes.
-----------------------------------------------------------------------

Enjoy,
  Dimitri

[Doxygen-users] Bug with enclosed classes and Alphabetical List?

[Pablo A. <alv...@te...>]

Hello everybody,

I have a problem sorting the classes in the "Alphabetical List".

I get the labels of A, B, A, B, A, B, A, where I expected something like
A, B, P.
A short example is included as attachment.  In our proyect with about
two hundred classes this "interesting" sorting is very confusing...  Am
I missing something in the configuration file or is this a bug?

Regards,

Pablo

-- =

Dipl.-Ing. Pablo Alvarado   <alv...@te...>
Lehrstuhl f=FCr Technische Informatik,    RWTH-Aachen
Ahornstr.55               Phone : ++49 241 80 23635
D-52074 Aachen            Fax   : ++49 241 80 22308

FW: [Doxygen-users] RTF output truncated ????

[Van K. S. <Ser...@cs...>]

Yep, I'm having the same problem with doxygen 1.2.10 on Win2K (got the
binaries, not the source). I ended up reverting to my older 1.2.8, but had
to write a little utility to fix the names of my dot graphs which did not
match the ones in the RTF image fields. Ouch.

-Serge

----- Original Message ----- 
From: "Joerg Meyer" <jm...@al...>
To: <dox...@li...>
Sent: Friday, September 28, 2001 8:03 AM
Subject: [Doxygen-users] RTF output truncated ????


> Hi,
> 
> I have been trying to produce RTF output from a small set (<10 files) of
> C++ header files that documented using the javadoc style. I am able to
> produce HTML, Latex (and PDF from that) just fine, so that everything
> that is defined in the header files shows up in the output. However,
> with the RTF output option a lot of stuff is missing. 
> 
> I tried it with just one input file but the same thing happened. It
> looks like as if it stopped producing output after a certain point.
> There are no error messages reported during the doxygen run.
> 
> Is this a known problem or has anybody experienced soemthing liek this
> before? If so, please let me know how you worked around it.
> 
> I am running doxygen 1.2.10 on a debian installation, kernel 2.2.19. 
> 
> Thanks in advance.
> 
> -Joerg
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 

[Doxygen-users] doxygen-1.2.10 partial specialization problem

[<nb...@fr...>]

Here is a test case showing a problem with partial specialization

template<typename T>
class Test {
public:
  //! general case
  template<typename X>
  void F (complex<T> t, X x);
};

template<typename T>
template<typename X>
void Test<T>::F (complex<T> t, X x) {}

//! specialization
template<>
template<typename X>
void Test< complex<int> >::F (complex<int> t, X x) {}

Here is the output:
[...]
Searching for member function documentation...
/home/nbecker/bitexact/Test.H:16: Warning: no matching class member found for 
  void Test::F(complex< int > t, X x)
Possible candidates:
  void F(complex< T > t, X x)

Re: [Doxygen-users] Buffer Overflow

[Dimitri v. H. <di...@st...>]

On Fri, Sep 28, 2001 at 05:13:26AM +0800, Stephen Morrison wrote:
> Hi,
> 
> I am getting this error in 1.2.10:
> 
> "input buffer overflow, can't enlarge buffer because scanner uses REJECT"
> when the tool is parsing a file.  Is this just a running out of memory
> issue?

See FAQ #12. If you have an example that produces this for another reason, 
please send it.

Regards,
  Dimitri

Re: [Doxygen-users] Which version of gviz, and why?

[Dimitri v. H. <di...@st...>]

On Fri, Sep 28, 2001 at 03:20:24PM +0100, Neil Salter wrote:
> Hello,
> 
> Which version of gviz/dot should I be using with doxygen?

I currently use 1.7.8 myself (on Linux). The docs still 
suggest version 1.5 but that's more because that part hasn't been
updated :-) Any version after 1.5 will probably work, but I have not much
control over the development on graphviz, so I cannot guarantee this.

Regards,
  Dimitri

Re: [Doxygen-users] RTF output truncated ????

[Dimitri v. H. <di...@st...>]

On Fri, Sep 28, 2001 at 08:03:07AM -0700, Joerg Meyer wrote:
> Hi,
> 
> I have been trying to produce RTF output from a small set (<10 files) of
> C++ header files that documented using the javadoc style. I am able to
> produce HTML, Latex (and PDF from that) just fine, so that everything
> that is defined in the header files shows up in the output. However,
> with the RTF output option a lot of stuff is missing. 
> 
> I tried it with just one input file but the same thing happened. It
> looks like as if it stopped producing output after a certain point.
> There are no error messages reported during the doxygen run.
> 
> Is this a known problem or has anybody experienced soemthing liek this
> before? If so, please let me know how you worked around it.
> 
> I am running doxygen 1.2.10 on a debian installation, kernel 2.2.19. 

I suggest to try the latest CVS version of doxygen. Some RTF output
problems have been fixed. If you still have problems, send me a small
example that allows me to reproduce the bug.

Regards,
  Dimitri

[Doxygen-users] RTF output truncated ????

[Joerg M. <jm...@al...>]

Hi,

I have been trying to produce RTF output from a small set (<10 files) of
C++ header files that documented using the javadoc style. I am able to
produce HTML, Latex (and PDF from that) just fine, so that everything
that is defined in the header files shows up in the output. However,
with the RTF output option a lot of stuff is missing. 

I tried it with just one input file but the same thing happened. It
looks like as if it stopped producing output after a certain point.
There are no error messages reported during the doxygen run.

Is this a known problem or has anybody experienced soemthing liek this
before? If so, please let me know how you worked around it.

I am running doxygen 1.2.10 on a debian installation, kernel 2.2.19. 

Thanks in advance.

-Joerg

RE: [Doxygen-users] Which version of gviz, and why?

[Catenacci, O. <Ono...@co...>]

Neil,
 
Why don't you try 1.7 and let us know what happens?  What's the worst that
could happen?
 

--
Onorio Catenacci
"People are more violently opposed to fur than leather because it's safer to
harass rich women than motorcycle gangs"

--Unknown 

-----Original Message-----
From: Neil Salter [mailto:ns...@ci...]
Sent: Friday, September 28, 2001 10:20 AM
To: dox...@li...
Subject: [Doxygen-users] Which version of gviz, and why?


Hello,

 
Which version of gviz/dot should I be using with doxygen?
 
I feel that this question must get asked a lot, but I can't find any record
of it, and have had a good look round for the answer. The mailing list
archive search seems to be broken just now (a problem with
''/bigassraid/htdig//conf/11668.conf", which sounds painful).

The doxygen page says use 1.5, but using it on a fairly sizeable project
here, I get a broken image on the graphical class hierarchy (I'm assuming
this is due to a bug in dot, and not doxygen).
 
The binary download for gviz 1.5 for Solaris has disappeared from the gviz
AT&T site, though there is a binary download for 1.7c. I remember it being
difficult to build 1.5 last time, so I grabbed the binary distro. Luckily I
still have it.
 
Nor could I find the Solaris 1.5 binary download on www.gviz.org
<http://www.gviz.org> .
 
Gviz seems to have moved into the 1.7's. Is there a problem using these with
doxygen. Has anyone tried it? Is there any reason I shouldn't be using the
latest stable version of gviz? Is this likely to change as gviz moves on?
 
Sorry if this has been asked before. Should it be a FAQ? It would be useful
to know why an older version (for which it's becoming tricky to get
binaries) should be used.
 
In closing, thanks very much to Dimitri and the doxygen contributors for
such a great tool! Great stuff.
 
Thanks in advance,
 
Neil.
 

[Doxygen-users] Which version of gviz, and why?

[Neil S. <ns...@ci...>]

Hello,

Which version of gviz/dot should I be using with doxygen?

I feel that this question must get asked a lot, but I can't find any =
record of it, and have had a good look round for the answer. The mailing =
list archive search seems to be broken just now (a problem with =
''/bigassraid/htdig//conf/11668.conf", which sounds painful).

The doxygen page says use 1.5, but using it on a fairly sizeable project =
here, I get a broken image on the graphical class hierarchy (I'm =
assuming this is due to a bug in dot, and not doxygen).

The binary download for gviz 1.5 for Solaris has disappeared from the =
gviz AT&T site, though there is a binary download for 1.7c. I remember =
it being difficult to build 1.5 last time, so I grabbed the binary =
distro. Luckily I still have it.

Nor could I find the Solaris 1.5 binary download on www.gviz.org.

Gviz seems to have moved into the 1.7's. Is there a problem using these =
with doxygen. Has anyone tried it? Is there any reason I shouldn't be =
using the latest stable version of gviz? Is this likely to change as =
gviz moves on?

Sorry if this has been asked before. Should it be a FAQ? It would be =
useful to know why an older version (for which it's becoming tricky to =
get binaries) should be used.

In closing, thanks very much to Dimitri and the doxygen contributors for =
such a great tool! Great stuff.

Thanks in advance,

Neil.

[Doxygen-users] RTF output incomplete

[Joerg M. <jm...@al...>]

Hi there,

I have been trying to produce RTF output from a small set of C++ header 
files but it doesn't list all the methods as defined in the header 
files. I tried to generate HTML, Latex and PDF and those work fine, the 
output files contain all the stuff that is defined in the header files.

Is this a known problem?

I am running doxygen 1.2.10 on debian (2.2.19).

Any hints? Do you need more info?

Thanks in advance.

   -Joerg

[Doxygen-users] Buffer Overflow

[Stephen M. <mor...@no...>]

Hi,

I am getting this error in 1.2.10:

"input buffer overflow, can't enlarge buffer because scanner uses REJECT"
when the tool is parsing a file.  Is this just a running out of memory
issue?

Regards

Stephen