doxygen-users Mailing List for Doxygen (Page 51)
Brought to you by:
dimitri
Menu
▾
▴
doxygen-users — List for users of doxygen
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(118) |
Jun
(150) |
Jul
(115) |
Aug
(75) |
Sep
(92) |
Oct
(102) |
Nov
(139) |
Dec
(87) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(131) |
Feb
(60) |
Mar
(114) |
Apr
(83) |
May
(125) |
Jun
(82) |
Jul
(95) |
Aug
(98) |
Sep
(109) |
Oct
(97) |
Nov
(72) |
Dec
(70) |
| 2003 |
Jan
(117) |
Feb
(122) |
Mar
(187) |
Apr
(114) |
May
(154) |
Jun
(131) |
Jul
(130) |
Aug
(98) |
Sep
(121) |
Oct
(107) |
Nov
(80) |
Dec
(54) |
| 2004 |
Jan
(78) |
Feb
(71) |
Mar
(118) |
Apr
(56) |
May
(56) |
Jun
(64) |
Jul
(164) |
Aug
(104) |
Sep
(101) |
Oct
(69) |
Nov
(107) |
Dec
(98) |
| 2005 |
Jan
(75) |
Feb
(77) |
Mar
(107) |
Apr
(114) |
May
(142) |
Jun
(106) |
Jul
(79) |
Aug
(108) |
Sep
(115) |
Oct
(140) |
Nov
(128) |
Dec
(63) |
| 2006 |
Jan
(86) |
Feb
(71) |
Mar
(125) |
Apr
(55) |
May
(48) |
Jun
(143) |
Jul
(99) |
Aug
(91) |
Sep
(93) |
Oct
(82) |
Nov
(46) |
Dec
(45) |
| 2007 |
Jan
(69) |
Feb
(97) |
Mar
(125) |
Apr
(112) |
May
(65) |
Jun
(80) |
Jul
(82) |
Aug
(84) |
Sep
(56) |
Oct
(74) |
Nov
(63) |
Dec
(74) |
| 2008 |
Jan
(161) |
Feb
(115) |
Mar
(58) |
Apr
(73) |
May
(58) |
Jun
(79) |
Jul
(57) |
Aug
(115) |
Sep
(79) |
Oct
(62) |
Nov
(93) |
Dec
(37) |
| 2009 |
Jan
(69) |
Feb
(115) |
Mar
(77) |
Apr
(85) |
May
(124) |
Jun
(58) |
Jul
(44) |
Aug
(85) |
Sep
(90) |
Oct
(80) |
Nov
(87) |
Dec
(48) |
| 2010 |
Jan
(52) |
Feb
(71) |
Mar
(54) |
Apr
(37) |
May
(66) |
Jun
(86) |
Jul
(84) |
Aug
(68) |
Sep
(94) |
Oct
(66) |
Nov
(36) |
Dec
(53) |
| 2011 |
Jan
(59) |
Feb
(77) |
Mar
(59) |
Apr
(67) |
May
(76) |
Jun
(54) |
Jul
(95) |
Aug
(92) |
Sep
(84) |
Oct
(72) |
Nov
(46) |
Dec
(60) |
| 2012 |
Jan
(43) |
Feb
(77) |
Mar
(88) |
Apr
(121) |
May
(81) |
Jun
(69) |
Jul
(97) |
Aug
(64) |
Sep
(55) |
Oct
(55) |
Nov
(38) |
Dec
(60) |
| 2013 |
Jan
(85) |
Feb
(70) |
Mar
(81) |
Apr
(83) |
May
(51) |
Jun
(65) |
Jul
(71) |
Aug
(39) |
Sep
(47) |
Oct
(32) |
Nov
(43) |
Dec
(28) |
| 2014 |
Jan
(64) |
Feb
(22) |
Mar
(54) |
Apr
(20) |
May
(59) |
Jun
(20) |
Jul
(50) |
Aug
(17) |
Sep
(37) |
Oct
(56) |
Nov
(40) |
Dec
(24) |
| 2015 |
Jan
(51) |
Feb
(29) |
Mar
(57) |
Apr
(31) |
May
(23) |
Jun
(50) |
Jul
(30) |
Aug
(66) |
Sep
(59) |
Oct
(21) |
Nov
(29) |
Dec
(12) |
| 2016 |
Jan
(33) |
Feb
(30) |
Mar
(19) |
Apr
(23) |
May
(16) |
Jun
(31) |
Jul
(17) |
Aug
(19) |
Sep
(21) |
Oct
(20) |
Nov
(15) |
Dec
(6) |
| 2017 |
Jan
(16) |
Feb
(13) |
Mar
(16) |
Apr
(23) |
May
(16) |
Jun
(5) |
Jul
(14) |
Aug
(13) |
Sep
(12) |
Oct
(11) |
Nov
(3) |
Dec
(6) |
| 2018 |
Jan
(4) |
Feb
(6) |
Mar
(5) |
Apr
(11) |
May
(26) |
Jun
(5) |
Jul
(10) |
Aug
(7) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
(7) |
| 2019 |
Jan
(17) |
Feb
(18) |
Mar
(5) |
Apr
(6) |
May
(3) |
Jun
|
Jul
(9) |
Aug
(19) |
Sep
(3) |
Oct
(1) |
Nov
(23) |
Dec
(5) |
| 2020 |
Jan
(7) |
Feb
(1) |
Mar
(7) |
Apr
(11) |
May
(8) |
Jun
(7) |
Jul
(10) |
Aug
(3) |
Sep
(4) |
Oct
(7) |
Nov
(6) |
Dec
|
| 2021 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(4) |
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(8) |
Dec
(3) |
| 2022 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(2) |
| 2023 |
Jan
(2) |
Feb
(5) |
Mar
(3) |
Apr
(7) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(5) |
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Matej K. <mat...@gm...> - 2014-11-24 19:36:03
|
Albert, That’s great! I can try new features as soon as they will be available. Regards, Matej > On 24. nov. 2014, at 19.13, Albert <alb...@gm...> wrote: > > Hi Matej, > > This is currently not possible, but I'm working on it (it will be similar to \image and also applicable for other external graphing commands) . Hopefully I can create a patch in the next few days. > > Albert > > On Mon, Nov 24, 2014 at 4:47 PM, Matej Kenda <mat...@gm...> wrote: > Hi, > > It is very nice that PlantUML keywords were integrated into Doxygen. > > Generated images are sometimes too wide and are not completely visible on the page. > > Is there a way to control the size of the generated images that are included into the Latex/PDF files in a similar fashion as it can be done for \image tags (witdh=\textwidth)? > |
|
From: Albert <alb...@gm...> - 2014-11-24 18:14:06
|
Hi Matej, This is currently not possible, but I'm working on it (it will be similar to \image and also applicable for other external graphing commands) . Hopefully I can create a patch in the next few days. Albert On Mon, Nov 24, 2014 at 4:47 PM, Matej Kenda <mat...@gm...> wrote: > Hi, > > It is very nice that PlantUML keywords were integrated into Doxygen. > > Generated images are sometimes too wide and are not completely visible on > the page. > > Is there a way to control the size of the generated images that are > included into the Latex/PDF files in a similar fashion as it can be done > for \image tags (witdh=\textwidth)? > > Thank you, > > Matej > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Matej K. <mat...@gm...> - 2014-11-24 15:47:37
|
Hi, It is very nice that PlantUML keywords were integrated into Doxygen. Generated images are sometimes too wide and are not completely visible on the page. Is there a way to control the size of the generated images that are included into the Latex/PDF files in a similar fashion as it can be done for \image tags (witdh=\textwidth)? Thank you, Matej |
|
From: Dimitri v. H. <do...@gm...> - 2014-11-18 18:40:59
|
This is a known bug, see also https://bugzilla.gnome.org/show_bug.cgi?id=735376 and it has been fixed in GitHub in the meantime by this commit https://github.com/doxygen/doxygen/commit/92eb236037e857f38eaf24238815641a48540792 Regards, Dimitri > On 18 Nov 2014, at 14:43 , didje <dia...@pd...> wrote: > > Hi, > In our system, we have a namespace ABC, which refers to std classes such as > List, Deque etc > > I generate a .tag file in the library TestLib, which uses some of these > classes. > > When I generated that .tag file with 1.8.7, I saw the following in the .tag > file: > > <compound kind="class"> > <name>ABC::Deque</name> > <filename>classABC_1_1Deque.html</filename> > <templarg></templarg> > <member kind="function"> > <type></type> > <name>Deque</name> > <anchorfile>classABC_1_1Deque.html</anchorfile> > <anchor>fghjfghjfghjygjfghjfghj</anchor> > <arglist>()</arglist> > </member> > </compound> > However, using the same sources, I generated the .tag file using 1.8.8 and > now the line is as follows: > <compound kind="singleton"> > <name>ABC::Deque</name> > <filename>classABC_1_1Deque.html</filename> > <templarg></templarg> > <member kind="function"> > <type></type> > <name>Deque</name> > <anchorfile>classABC_1_1Deque.html</anchorfile> > <anchor>fghjfghjfghjygjfghjfghj</anchor> > <arglist>()</arglist> > </member> > </compound> > > I don't know what made the compound kind change to a "singleton". > > Various other libraries access the TestLib.tag file in the TestLib library. > However, when they do so, warning messages appear, as follows: > ~/doc/library/TestLib/TestLib.tag:1655: warning: Unknown compound attribute > `singleton' found! > ~/doc/library/TestLib/TestLib.tag:1656: warning: Unexpected tag `name' found > ~/doc/library/TestLib/TestLib.tag:1657: warning: Unexpected tag `filename' > found > ~/doc/library/TestLib/TestLib.tag:1658: warning: Unexpected tag `templarg' > found > ~/doc/library/TestLib/TestLib.tag:1705: warning: Unexpected tag `member' > found > ~/doc/library/TestLib/TestLib.tag:1706: warning: tag `compound' was not > expected! > > Why is the class Deque being called a singleton in 1.8.8, but was not in > 1.8.7? > Also, why are there warning messages for the singleton in 1.8.8 ? > > Thanks for any help. > > > > -- > View this message in context: http://doxygen.10944.n7.nabble.com/Mysterious-singleton-in-tag-file-causes-warnings-tp6920.html > Sent from the Doxygen - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users |
|
From: didje <dia...@pd...> - 2014-11-18 13:50:08
|
Hi, In our system, we have a namespace ABC, which refers to std classes such as List, Deque etc I generate a .tag file in the library TestLib, which uses some of these classes. When I generated that .tag file with 1.8.7, I saw the following in the .tag file: <compound kind="class"> <name>ABC::Deque</name> <filename>classABC_1_1Deque.html</filename> <templarg></templarg> <member kind="function"> <type></type> <name>Deque</name> <anchorfile>classABC_1_1Deque.html</anchorfile> <anchor>fghjfghjfghjygjfghjfghj</anchor> <arglist>()</arglist> </member> </compound> However, using the same sources, I generated the .tag file using 1.8.8 and now the line is as follows: <compound kind="singleton"> <name>ABC::Deque</name> <filename>classABC_1_1Deque.html</filename> <templarg></templarg> <member kind="function"> <type></type> <name>Deque</name> <anchorfile>classABC_1_1Deque.html</anchorfile> <anchor>fghjfghjfghjygjfghjfghj</anchor> <arglist>()</arglist> </member> </compound> I don't know what made the compound kind change to a "singleton". Various other libraries access the TestLib.tag file in the TestLib library. However, when they do so, warning messages appear, as follows: ~/doc/library/TestLib/TestLib.tag:1655: warning: Unknown compound attribute `singleton' found! ~/doc/library/TestLib/TestLib.tag:1656: warning: Unexpected tag `name' found ~/doc/library/TestLib/TestLib.tag:1657: warning: Unexpected tag `filename' found ~/doc/library/TestLib/TestLib.tag:1658: warning: Unexpected tag `templarg' found ~/doc/library/TestLib/TestLib.tag:1705: warning: Unexpected tag `member' found ~/doc/library/TestLib/TestLib.tag:1706: warning: tag `compound' was not expected! Why is the class Deque being called a singleton in 1.8.8, but was not in 1.8.7? Also, why are there warning messages for the singleton in 1.8.8 ? Thanks for any help. -- View this message in context: http://doxygen.10944.n7.nabble.com/Mysterious-singleton-in-tag-file-causes-warnings-tp6920.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
|
From: Anthony F. <ant...@gm...> - 2014-11-18 06:59:42
|
On Mon, Nov 17, 2014 at 10:06 AM, Albert <alb...@gm...> wrote: > You wrote about Fedora 20: "The versions are more up-to-date" but I see > that doxygen is version 1.8.6 whilst the current version is 1.8.8, might > make a difference. Same accounts probably for the texlive version. I don't > think the graphviz program will be a problem (current version is 2.38). > Good point; I'll try to test with more current versions in the next few days. > Would be good to have a small example to be able to reproduce the problem. > I'll see if I can come up with a representative sample. Thanks! |
|
From: Albert <alb...@gm...> - 2014-11-17 18:06:23
|
You wrote about Fedora 20: "The versions are more up-to-date" but I see
that doxygen is version 1.8.6 whilst the current version is 1.8.8, might
make a difference. Same accounts probably for the texlive version. I don't
think the graphviz program will be a problem (current version is 2.38).
Would be good to have a small example to be able to reproduce the problem.
On Sun, Nov 16, 2014 at 11:27 PM, Anthony Foiani <ant...@gm...>
wrote:
> On Sun, Nov 16, 2014 at 2:06 PM, Anthony Foiani <ant...@gm...>
> wrote:
>
>> (I'm about to try it on a Fedora 20 system, just in case it's slightly
>> more up-to-date...)
>>
>
> The versions are more up-to-date, but same error occurs:
>
> pdfTeX warning: pdflatex (file ./dc/d1e/CompositeKey_8hpp__dep__incl.pdf):
> PDF
> inclusion: multiple pdfs with page group included in a single page
> >]
> Underfull \hbox (badness 10000) detected at line 25
> [][][]
> ) (./d1/d16/CondVar_8hpp.tex
> <d2/dfa/CondVar_8hpp__incl.pdf, id=76097, 172.645pt x 156.585pt>
> <use d2/dfa/CondVar_8hpp__incl.pdf>
> ! Dimension too large.
> <argument> \wd \@tempboxa
>
> l.23 ...dth=350pt]{d8/d63/CondVar_8hpp__dep__incl}
> ?
>
> Versions:
>
> $ rpm -qa | egrep -i 'doxygen|pdf.*tex|tex.*pdf|graphviz'
> texlive-dvipdfmx-svn32380.0-5.fc20.noarch
> doxygen-1.8.6-1.fc20.x86_64
> texlive-mptopdf-bin-svn18674.0-5.20131226_r32488.fc20.noarch
> texlive-pst-pdf-svn31660.1.1v-5.fc20.noarch
> texlive-mptopdf-svn29751.0-5.fc20.noarch
> texlive-pdftex-svn32380.1.40.11-5.fc20.noarch
> texlive-pdftex-def-svn22653.0.06d-5.fc20.noarch
> texlive-thumbpdf-svn29725.3.15-5.fc20.noarch
> texlive-dvipdfmx-def-svn31722.0-5.fc20.noarch
> graphviz-2.34.0-8.fc20.x86_64
> texlive-pst-pdf-bin-svn7838.0-5.20131226_r32488.fc20.noarch
> texlive-dvipdfmx-bin-svn30845.0-5.20131226_r32488.fc20.x86_64
> texlive-pdftex-bin-svn30845.0-5.20131226_r32488.fc20.x86_64
> texlive-thumbpdf-bin-svn6898.0-5.20131226_r32488.fc20.noarch
> texlive-auto-pst-pdf-svn23723.0.6-5.fc20.noarch
> texlive-pdfpages-svn31518.0.4v-5.fc20.noarch
>
> Again, any hints are appreciated.
>
> Thanks!
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>
|
|
From: Anthony F. <ant...@gm...> - 2014-11-16 22:27:11
|
On Sun, Nov 16, 2014 at 2:06 PM, Anthony Foiani <ant...@gm...>
wrote:
> (I'm about to try it on a Fedora 20 system, just in case it's slightly
> more up-to-date...)
>
The versions are more up-to-date, but same error occurs:
pdfTeX warning: pdflatex (file ./dc/d1e/CompositeKey_8hpp__dep__incl.pdf):
PDF
inclusion: multiple pdfs with page group included in a single page
>]
Underfull \hbox (badness 10000) detected at line 25
[][][]
) (./d1/d16/CondVar_8hpp.tex
<d2/dfa/CondVar_8hpp__incl.pdf, id=76097, 172.645pt x 156.585pt>
<use d2/dfa/CondVar_8hpp__incl.pdf>
! Dimension too large.
<argument> \wd \@tempboxa
l.23 ...dth=350pt]{d8/d63/CondVar_8hpp__dep__incl}
?
Versions:
$ rpm -qa | egrep -i 'doxygen|pdf.*tex|tex.*pdf|graphviz'
texlive-dvipdfmx-svn32380.0-5.fc20.noarch
doxygen-1.8.6-1.fc20.x86_64
texlive-mptopdf-bin-svn18674.0-5.20131226_r32488.fc20.noarch
texlive-pst-pdf-svn31660.1.1v-5.fc20.noarch
texlive-mptopdf-svn29751.0-5.fc20.noarch
texlive-pdftex-svn32380.1.40.11-5.fc20.noarch
texlive-pdftex-def-svn22653.0.06d-5.fc20.noarch
texlive-thumbpdf-svn29725.3.15-5.fc20.noarch
texlive-dvipdfmx-def-svn31722.0-5.fc20.noarch
graphviz-2.34.0-8.fc20.x86_64
texlive-pst-pdf-bin-svn7838.0-5.20131226_r32488.fc20.noarch
texlive-dvipdfmx-bin-svn30845.0-5.20131226_r32488.fc20.x86_64
texlive-pdftex-bin-svn30845.0-5.20131226_r32488.fc20.x86_64
texlive-thumbpdf-bin-svn6898.0-5.20131226_r32488.fc20.noarch
texlive-auto-pst-pdf-svn23723.0.6-5.fc20.noarch
texlive-pdfpages-svn31518.0.4v-5.fc20.noarch
Again, any hints are appreciated.
Thanks!
|
|
From: Anthony F. <ant...@gm...> - 2014-11-16 21:07:03
|
My HTML output is fine, and now I'm trying to build PDF output. `pdflatex`
halts with this error:
pdfTeX warning: pdflatex (file ./de/dac/ByteBuffer_8hpp__dep__incl.pdf):
PDF in
clusion: multiple pdfs with page group included in a single page
>]) (./d8/df5/ByteBufferTest_8cpp.tex
<d9/d96/ByteBufferTest_8cpp__incl.pdf, id=75842, 1036.87375pt x 381.425pt>
<use d9/d96/ByteBufferTest_8cpp__incl.pdf> [2424
<./d9/d96/ByteBufferTest_8cpp_
_incl.pdf>]) (./dc/d1e/CharBuffer_8hpp.tex
<d6/d8d/CharBuffer_8hpp__dep__incl.pdf, id=75896, 10483.165pt x 1035.87pt>
<use d6/d8d/CharBuffer_8hpp__dep__incl.pdf> [2425
<./d6/d8d/CharBuffer_8hpp__de
p__incl.pdf>]) (./d5/dba/CharBufferTest_8cpp.tex
<d8/dad/CharBufferTest_8cpp__incl.pdf, id=75935, 820.06375pt x 381.425pt>
<use d8/dad/CharBufferTest_8cpp__incl.pdf> [2426
<./d8/dad/CharBufferTest_8cpp_
_incl.pdf>]) (./d3/d84/CompositeKey_8hpp.tex
<dc/d1e/CompositeKey_8hpp__dep__incl.pdf, id=75965, 13643.97375pt x
337.26pt>
<use dc/d1e/CompositeKey_8hpp__dep__incl.pdf>) (./d1/d01/CondVar_8cpp.tex
<de/d4d/CondVar_8cpp__incl.pdf, id=75968, 561.09625pt x 212.795pt>
<use de/d4d/CondVar_8cpp__incl.pdf>
Underfull \vbox (badness 1874) has occurred while \output is active [2427
<./dc
/d1e/CompositeKey_8hpp__dep__incl.pdf>]) (./d1/d16/CondVar_8hpp.tex
<d2/dfa/CondVar_8hpp__incl.pdf, id=76003, 172.645pt x 156.585pt>
<use d2/dfa/CondVar_8hpp__incl.pdf>
! Dimension too large.
<argument> \wd \@tempboxa
l.23 ...dth=350pt]{d8/d63/CondVar_8hpp__dep__incl}
?
Any suggestions on how to debug this further?
I found a few reports of the "multiple pdfs with page group included in a
single page" warning, but they don't seem to be the likely cause of this
issue. (If nothing else, I get dozens or hundreds of those warnings, but
this is the first place it halts.)
Some of my dependency / usage graphs are pretty huge, but I would hope that
the PDF version would just scale those down to uselessness, not error out.
System is fully-up-to-date Fedora 19 x86_64; the relevant packages are
hopefully:
$ rpm -qa | egrep -i 'doxygen|pdf.*tex|tex.*pdf|graphviz'
doxygen-1.8.3.1-2.fc19.x86_64
texlive-dvipdfmx-bin-svn30205.0-0.1.20130608_r30832.fc19.x86_64
texlive-pdftex-bin-svn30088.0-0.1.20130608_r30832.fc19.x86_64
texlive-thumbpdf-svn29725.3.15-0.1.fc19.noarch
texlive-dvipdfmx-svn30386.0-0.1.fc19.noarch
texlive-thumbpdf-bin-svn6898.0-0.1.20130608_r30832.fc19.noarch
graphviz-2.30.1-12.fc19.x86_64
texlive-mptopdf-bin-svn18674.0-0.1.20130608_r30832.fc19.noarch
texlive-pdftex-svn30753.1.40.11-0.1.fc19.noarch
texlive-mptopdf-svn29751.0-0.1.fc19.noarch
texlive-dvipdfmx-def-svn30729.0-0.1.fc19.noarch
texlive-pdftex-def-svn22653.0.06d-0.1.fc19.noarch
texlive-pdfpages-svn27574.0.4t-0.1.fc19.noarch
Thanks for any suggestions!
(I'm about to try it on a Fedora 20 system, just in case it's slightly more
up-to-date...)
Thanks again,
Anthony
|
|
From: Tanaka S. <ta...@gm...> - 2014-11-16 18:17:24
|
Thank you Albert. I would like stress that I had to give all the namespaces my class was hidden in, e.g.: \ref namespace1::namespace2::myclass otherwise myclass won't be found by doxygen. simon On 16.11.2014 09:15, Albert wrote: > Please have a look at the documentation "Automatic link generation" > (in pdf chapter 11) and "Links to classes (in pdf paragraph 11.2). > > On Sat, Nov 15, 2014 at 11:56 PM, Tanaka Simon <ta...@gm... > <mailto:ta...@gm...>> wrote: > > Dear doxygen Users, > > For the doxygen documentation, I have a html Mainpage.dox file. If > a source code file name is written in it, hyperlinks to that > source file are automatically generated. > > But how can I have a hyperlink to to a class definition, or member > method, or the like? > > > A minimal example is attached. > > Thanks > Simon > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push > notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > <mailto:Dox...@li...> > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Shyamal C. <shy...@gm...> - 2014-11-16 14:55:13
|
Hi, When will there be support for other languages like LISP and Scheme? Thanks! Best, Shyamal Chandra shy...@gm... |
|
From: Albert <alb...@gm...> - 2014-11-16 08:15:52
|
Please have a look at the documentation "Automatic link generation" (in pdf chapter 11) and "Links to classes (in pdf paragraph 11.2). On Sat, Nov 15, 2014 at 11:56 PM, Tanaka Simon <ta...@gm...> wrote: > Dear doxygen Users, > > For the doxygen documentation, I have a html Mainpage.dox file. If a > source code file name is written in it, hyperlinks to that source file are > automatically generated. > > But how can I have a hyperlink to to a class definition, or member method, > or the like? > > > A minimal example is attached. > > Thanks > Simon > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Tanaka S. <ta...@gm...> - 2014-11-15 22:56:32
|
Dear doxygen Users, For the doxygen documentation, I have a html Mainpage.dox file. If a source code file name is written in it, hyperlinks to that source file are automatically generated. But how can I have a hyperlink to to a class definition, or member method, or the like? A minimal example is attached. Thanks Simon |
|
From: Matt <m_...@ya...> - 2014-11-14 02:52:59
|
Hi, I was wondering if anyone can help me with customizing the layout.xml file to get a reasonable-looking details at top style layout. I have already moved the "Detailed Description" section to the top, but it doesn't quite hang together properly. There are two things I want to change: 1). The "More..." link on the brief description still points to the Detailed Description section. I'd love to change this to a "Reference..." link which would point to the section after Detailed Description. 2). Get rid of the "Detailed Description" title. It doesn't make any sense to have this title when the detailed description follows directly on from the brief description, and yet I can't work out how to get rid of it. Are there any attributes I can change in the layout.xml file to achieve these things? I can't find any reference docs for the attribute values. Thanks for reading my post -- View this message in context: http://doxygen.10944.n7.nabble.com/Customizing-layout-xml-for-Details-at-top-style-tp6911.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
|
From: Joseph C. <jc...@en...> - 2014-11-14 01:07:56
|
I'm trying to use a code block in a VHDL, but I can't seem to get it working. I think I'm following the documentation correctly by indenting 4 spaces relative to the previous paragraph). I've attached my example test.vhd, Doxyfile, and doxygen output. Could someone tell me what I'm doing wrong? Or if this is a missing feature for VHDL in doxygen? Thanks, Joseph P.S. My attachment is a regular .zip, but I had to rename it to .zipped so Gmail wouldn't block it. Also, I've only included the html file output to avoid going over the 60kB attachment limit. |
|
From: Albert <alb...@gm...> - 2014-11-13 18:18:23
|
The pdf documentation can be generated by setting GENERATE_LATEX to YES in the Doxyfile and after the doxygen command go to the latex directory and give here the command make. In the manual there are also some extra options mentioned for fine tuning your documentation. For the requirements to generate the pdf output see the manual (search e.g. for pdflatex). Btw. the doxygen manual is also generated with the aid of doxygen and generating the pdf version is done in similar way as described above. On Thu, Nov 13, 2014 at 9:26 AM, Niels Grundtvig Nielsen < com...@gm...> wrote: > I've walked into the middle of a long-running project, where one customer > is now expressing a strong preference for .pdf instead of .chm > > The developers say they gave up on trying to produce .pdf output, because > they were not getting hyperlinks in the body or a clickable ToC. I'm hoping > this is just a question of finding out how to enable these output options … > > Can someone can tell me exactly what steps we need to take to convert > Doxygen latex output – hope I've understood things thus far! it's my first > encounter with Doxygen – into a normal, full-featured .pdf? thanks in > advance. > > Niels Grundtvig Nielsen > technical communicator > *you know what you're talking about – I can help you say it* > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Paul A. L. <pa...@le...> - 2014-11-13 16:13:24
|
Hi everyone.
We are currently using SVG figures, typically drawn in Inkscape, in our
markdown-written doxygen-generated documentation. For example:
@image latex figures/something.pdf "Foo bar"
However, it would be awesome if we could get away with creating only
something.svg manually and not having to create the something.pdf file
in a separate step. We figured we'd get away with running a script that
would generate the PDF files, but doxygen doesn't insert an
\includegraphics command for SVG files.
For the same reason, we can't simply reprogram the LaTeX command
\includegraphics{..} to call the \includesvg{..} command, which resides
in a separate package.
What would an optimal solution be? We would be willing to run a figure
generation (bash/python/similar) script when building, but, as stated,
would prefer not having to create duplicate figure files.
Cheers,
Paul.
|
|
From: Niels G. N. <com...@gm...> - 2014-11-13 08:26:51
|
I've walked into the middle of a long-running project, where one customer is now expressing a strong preference for .pdf instead of .chm The developers say they gave up on trying to produce .pdf output, because they were not getting hyperlinks in the body or a clickable ToC. I'm hoping this is just a question of finding out how to enable these output options … Can someone can tell me exactly what steps we need to take to convert Doxygen latex output – hope I've understood things thus far! it's my first encounter with Doxygen – into a normal, full-featured .pdf? thanks in advance. Niels Grundtvig Nielsen technical communicator *you know what you're talking about – I can help you say it* |
|
From: Jens F. <fra...@st...> - 2014-11-11 14:47:46
|
Since the discussion and workarounds in Getting shared_ptr refs to appear in collaboration diagrams..... Eric J. Holtman 2010-03-01 and Re: templates and association diagrams James Ahlborn 2004-08-04 there is now the C++C11 standard (and one dos not need boost for certain smart pointer anymore) and I am still searching for an solution which is showing an embedded class object by a smart pointer (std::shared_ptr, std::week_ptr, std::unique_ptr) like a usual raw pointer. When generating UML look diagrams raw pointer s are indicated which the usually diamond symbol, but classed embedded by smart pointers are not shown. The workarounds managed in the post above are not solving the problem because they are showing an intermediate object "shared_ptr" between class and embedded class object. Since smart pointer can be use like raw pointers (and provide a lot of advantages) they should be treated like raw pointers. Maybe there are some good reasons that doxygen will not show all classes embedded in containers. |
|
From: François M. <gri...@gm...> - 2014-11-10 16:41:02
|
Hi, I have posted my issue on StackOverflow but I haven't had any feedback. http://stackoverflow.com/questions/26846859/doxygen-custom-cross-reference-page-shows-namespace-instead-of-class-names-php I have namespaced PHP classes documented as such: <?php namespace container; /** * Description of Stuff * * \xrefitem wpaction "Actions" "Actions Wordpress" init */ class Stuff {} Other example: <?phpnamespace container; /** * Description of Things * * \xrefitem wpaction "Actions" "Actions Wordpress" admin */class Things {} They are cross-referenced in the page defined as such: /** * \page wpaction Wordpress actions * * All Wordpress actions used by ACME software. */ The problem is that, instead of class names, only the container namespace appears in the Doxygen generated cross-reference page. container\Stuff and container\Things should appear instead. Is this a bug or am I doing something wrong? How can I fix this? (I use ALIASES to shorten calls to \xrefitem in production code, but I omitted it in this test case to narrow down the problem.) Thanks for your time, -- François Moreau |
|
From: marco r. <mre...@gm...> - 2014-11-10 15:44:16
|
Hi, with \section, \subsection etc. doxygen uses the whole line as arguments. Is it possible to have a title spanning multiple lines, such as \section name_of_the_section A rather long section title Thanks you, Marco |
|
From: Komal S <kom...@ya...> - 2014-11-09 23:27:59
|
Hi Albert, Setting CREATE_SUBDIRS to NO worked for me. Thank you for your help with this. Komal -- View this message in context: http://doxygen.10944.n7.nabble.com/for-page-numbers-in-the-indices-tp6895p6902.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
|
From: Albert <alb...@gm...> - 2014-11-09 18:57:10
|
Hi Komal,
Got the mail.
Problem here is the CREATE_SUBDIRS in case this is set to NO everything is
working fine.
A bit more details: the \pageref refers with CREATE_SUBDIRS set to YES to
dc/d42/group___main whilst the \hypertarget, \newlabel or \label refer to
group___main.
I can vaguely remember that I worked on a similar problem in the past
regarding links to other objects.
Currently I'm working on some other issues regarding latex output so I
cannot do a full check and create a patch. There are 3 places where
\pageref is used but when taking the current source version and replacing
in latexgen.cpp line1091:
t << "}{\\pageref{" << fn << "}}{}" << endl;
by
t << "}{\\pageref{" << stripPath(fn) << "}}{}" << endl;
your problem will be solved.
Albert
On Sun, Nov 9, 2014 at 5:31 PM, Komal S <kom...@ya...> wrote:
> Hello ALbert,
>
> I have subscribed to this mailing list and have attached my tree.
>
> Thanks
> Komal
>
> DocGen.zip <http://doxygen.10944.n7.nabble.com/file/n6900/DocGen.zip>
>
>
>
> --
> View this message in context:
> http://doxygen.10944.n7.nabble.com/for-page-numbers-in-the-indices-tp6895p6900.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
|
|
From: Komal S <kom...@ya...> - 2014-11-09 16:37:21
|
Hello ALbert, I have subscribed to this mailing list and have attached my tree. Thanks Komal DocGen.zip <http://doxygen.10944.n7.nabble.com/file/n6900/DocGen.zip> -- View this message in context: http://doxygen.10944.n7.nabble.com/for-page-numbers-in-the-indices-tp6895p6900.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
|
From: albert <alb...@gm...> - 2014-11-08 09:07:09
|
Hi Komal, In the source tree that I have I don't see the problem, so your minimal example including Doxyfile would be nice to have to reproduce your problem. Either attach it here or file a bug report at bugzilla. Before replying to this email please register at this mailing list as otherwise no mail notification is send out by default and the message won't always be read or with a possible large delay. Albert -- View this message in context: http://doxygen.10944.n7.nabble.com/for-page-numbers-in-the-indices-tp6895p6899.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
194 messages has been excluded from this view by a project administrator.
