Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 1530: Refactor, Document Member, only in impl.
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

drzoom
Ketchup Master

Switzerland
57 Posts

Posted - Jul 19 2006 :  05:11:49 AM  Show Profile  Reply with Quote

It' seems that the "Document Member" function only works in the implementation file.

I personally document all members in the header file, and use the Doxygen or Javadoc syntax:


/**
 * \\short A short introduction
 * 
 * Longer description
 * 
 * \\date 2007-07-19
 * \\author NameofAuthor
 * \\param a The description for parameter a
 * \\param b The description for parameter b
 * \\param c The description for parameter c
 * \\param d The description for parameter d
 * \\return A description of the return value.
 */


Or the same Javadoc compatible:


/**
 * A short introduction.
 * 
 * Longer description
 * 
 * @date 2007-07-19
 * @author NameofAuthor
 * @param a The description for parameter a
 * @param b The description for parameter b
 * @param c The description for parameter c
 * @param d The description for parameter d
 * @return A description of the return value.
 */


I found no way how to change the autotext entry to create this kind of output.


  • I don't need the type only the name (Doxygen extracts this information from the code)

  • \\return should only appear, if there is another return value as void

  • A default description "ctor" and "dtor" for constructors/destructors



There is another problem with the return value:


namespace x {
namespace y {

//************************************
// Method:    foo
// FullName:  x::y::Foo::foo
// Access:    private 
// Returns:   void Foo::
// Qualifier: 
// Parameter: X hiSide
// Parameter: Y slot1
// Parameter: Y slot2
// Parameter: Y slot3
// Parameter: Y right1
// Parameter: Y left1
// Parameter: Y right2
// Parameter: Y left2
// Parameter: Y right3
// Parameter: Y left3
//************************************
void Foo::foo(
	X hiSide,
	Y slot1,
	Y slot2,
	Y slot3,
	Y right1, Y left1,
	Y right2, Y left2,
	Y right3, Y left3 )
{


The name of the class is copied into the return value.


best regards
Tobias

feline
Whole Tomato Software

United Kingdom
19020 Posts

Posted - Jul 20 2006 :  5:54:24 PM  Show Profile  Reply with Quote
Document Method not working in the header file is on the list

case=1726

new autotext tags for the parameters without the types are due in the next build

case=1211

i have thought about the unnecessary return line myself, so i have put in a feature request:

case=1755

where you say "A default description 'ctor' and 'dtor' for constructors/destructors" i don't understand what you are after.

the problem with return value in a namespace is covered (i think) by

case=1727

zen is the art of being at one with the two'ness
Go to Top of Page

drzoom
Ketchup Master

Switzerland
57 Posts

Posted - Jul 21 2006 :  03:16:13 AM  Show Profile  Reply with Quote
Because many classes simple have a very simple constructor and deconstructor, I used to document them with a default text like 'ctor' and 'dtor'. This is only for completeness of the documentation, to shorten something like "The constructor constructs an instance of Object 'Foo'"..

So it would be nice, if VA detects that the documented member is a constructor or a deconstructor, and default text like 'ctor' or 'dtor' is filled in the documentation block.

More advanced would be detection of the copy constructor ('copy ctor') :-)

best regards
Tobias
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
19020 Posts

Posted - Jul 22 2006 :  12:31:55 PM  Show Profile  Reply with Quote
for now i would suggest you try using autotext. try setting up two or three standard comments, like this, and use the same shortcut for all of them, perhaps "///"

then when you type this you get a listbox, allowing you to select the comment you want to insert.

i am very wary of the concept of document method behaving differently for different types of functions like this, since it starts to be come much harder to support, and opens the door to all sorts of "odd" feature requests for other custom function types.

zen is the art of being at one with the two'ness
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Aug 08 2006 :  01:13:09 AM  Show Profile  Reply with Quote
Cases 1211, 1726 and 1727 are fixed in 1531.

Edited by - support on Aug 08 2006 01:15:19 AM
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000