Re: [Doxygen-users] Hide 'Class List' (Rachel)
Brought to you by:
dimitri
From: Harpreet S. A. <har...@no...> - 2011-04-07 13:25:08
|
Hi Rachel, There is no such tag. But, you can hide the class list via custom layout file. 1. Generate layout file doxygen -l layout.xml 2. Edit that layout file. <tab type="classes" visible="yes" title=""> Set visible to "no" 3. Pass the custom layout file in doxyfile via LAYOUT_FILE tag. LAYOUT_FILE = ./layout.xml Regards, Harpreet Singh -----Original Message----- From: dox...@li... [mailto:dox...@li...] Sent: Thursday, April 07, 2011 4:39 PM To: dox...@li... Subject: Doxygen-users Digest, Vol 59, Issue 2 Send Doxygen-users mailing list submissions to dox...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/doxygen-users or, via email, send a message with subject or body 'help' to dox...@li... You can reach the person managing the list at dox...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Doxygen-users digest..." Today's Topics: 1. Re: Missing included_by graphs (Ian Britten) 2. preprocessing #ifdefs within doxygen comments (FloofLeBo) 3. Hide 'Class List' (Rachel) 4. Doxygen 1.7.2 broken or am I using it wrong? (Jaco Naude) ---------------------------------------------------------------------- Message: 1 Date: Mon, 04 Apr 2011 16:56:22 -0300 From: Ian Britten <br...@ca...> Subject: Re: [Doxygen-users] Missing included_by graphs To: dox...@li... Message-ID: <4D9...@ca...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 04/04/11 04:47 PM, Dimitri Van Heesch wrote: > There was a problem with #include dependencies indeed. > Should be fixed in 1.7.4 though, so I suggest to upgrade to that version. Dimitri, Many thanks for the quick response! I saw a bug or two in the database related to includes, but nothing that sounded like the problem I was seeing... As soon as I can track down an RPM (for IT), I'll give it a try.. Keep up the great work! Ian ------------------------------ Message: 2 Date: Tue, 5 Apr 2011 05:05:09 -0700 (PDT) From: FloofLeBo <blu...@ya...> Subject: [Doxygen-users] preprocessing #ifdefs within doxygen comments To: dox...@li... Message-ID: <313...@ta...> Content-Type: text/plain; charset=us-ascii Hi all, I'm having the following problem with doxygen: In a library i'm building, I use preprocessor #defines to enable/disable modules What I'd like is to generate a different documentation depending on these defines. On my mainpage, I have a summary with links [code] /** @mainpage MyLibrary Welcome Developers! <p> Welcome to MyLibrary's documentation <h2>Table of contents</h2> -# @subpage Introduction -# @ref IntroducingMyLibrary -# @subpage Modules -# @ref ModuleIntroduction #ifdef MY_MODULE_1 -# @ref Module1 #endif // MY_MODULE_1 #ifdef MY_MODULE_2 -# @ref Module2 #endif // MY_MODULE_2 #ifdef MY_MODULE_3 -# @ref Module3 #endif // MY_MODULE_3 -# @subpage FAQ */ [/code] but unfortunately, doxygen does not preprocess my conditionals within comments. Is there a way to do something like that ? Thanks -- View this message in context: http://old.nabble.com/preprocessing--ifdefs-within-doxygen-comments-tp31322809p31322809.html Sent from the Doxygen - Users mailing list archive at Nabble.com. ------------------------------ Message: 3 Date: Tue, 5 Apr 2011 15:31:08 +0000 (UTC) From: Rachel <rs...@ac...> Subject: [Doxygen-users] Hide 'Class List' To: dox...@li... Message-ID: <loo...@po...> Content-Type: text/plain; charset=us-ascii Hi, The Build option, Show_Directories can be set to YES to display the Directory tab, which shows the directory hierarchy in the documentation. Setting it to NO hides the Directory tab in the documentation. Is there an equivalent tag that can be set to hide the Class List tab? Thank you. ------------------------------ Message: 4 Date: Thu, 7 Apr 2011 11:09:05 +0000 From: Jaco Naude <nau...@gm...> Subject: [Doxygen-users] Doxygen 1.7.2 broken or am I using it wrong? To: dox...@li... Message-ID: <BAN...@ma...> Content-Type: text/plain; charset="iso-8859-1" Hi I've used doxygen for a year or so on a biggish open source project. I'm not sure when it happened but I've found that it generates wrong outputs for some classes. For example, consider this class: http://gitorious.org/qtilities/qtilities/blobs/master/src/Core/source/SubjectIterator.h http://gitorious.org/qtilities/qtilities/blobs/master/src/Core/source/TreeIterator.h The SubjectIterator does not appear in my output docs but the TreeIterator appears correctly. See the namespace: http://www.qtilities.org/docs_master/namespace_qtilities_1_1_core.html. Clearly the TreeIterator is there but not the SubjectIterator. Maybe its the template thats confusing me or doxygen, but it does not only happen for template classes. Then I realized that some functions of the SubjectIterator appears under the Qtilities namespace, see http://www.qtilities.org/docs_master/namespace_qtilities.html. It adds garbage to the Qtilities namespace, for example: Qtilities::__pad0__ You will also notice other random things under the Qtilities namespace which should not be there. Any ideas on whats going wrong would be appreciated. My doxyfile is attached. Thanks Jaco -------------- next part -------------- An HTML attachment was scrubbed... -------------- next part -------------- A non-text attachment was scrubbed... Name: doxyfile_website_with_tracking Type: application/octet-stream Size: 11255 bytes Desc: not available ------------------------------ ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ------------------------------ _______________________________________________ Doxygen-users mailing list Dox...@li... https://lists.sourceforge.net/lists/listinfo/doxygen-users End of Doxygen-users Digest, Vol 59, Issue 2 ******************************************** ________________________________ NOTE: This message and its attachments are intended only for the individual or entity to which it is addressed and may contain confidential information or forward-looking statements regarding product development. Forward-looking statements are subject to change at Atrenta's sole discretion and Atrenta will have no liability for the delay or failure to deliver any product or feature mentioned in such forward-looking statements. |