V19 javadoc comment skeleton

[jnairb]

When I start a javadoc comment for a function with no parameters, the javadoc skeleton includes an empty @param. This didn't happen in VS18.

For example, starting with

Code: [Select]

/**[cursor]*/
void func();

and pressing enter, expands to

Code: [Select]

/**
 *
 * @param 
 */
void func();

Also, for functions that do have parameters, if I use the javadoc-editor to enter a javadoc comment, it aligns the parameter descriptions in the same column normally. The javadoc skeleton that's entered automatically inserts "tab stops" for each parameter description, but they're not aligned. And because of these "tab stops", I can't use tab to move to a common column for my descriptions. Is there any way to get the tab stops aligned after the parameter names?

[Clark]

Reproduced. We will look into this.

[patrick]

The problem with the blank @param line should be fixed for the next release candidate.

Those tabs you're seeing are called hotspots.  There's a global on/off for them in the options dialog under Editing -> Hotspots.  If you just don't want them in your comment expansion, you can go to Document -> C++ options in your menu, select "Comments", and then click on the "Edit Expansion" button on the right hand side of the page.  In the javadoc comment, you can remove the "%\c" from the @param line, and you'll no longer get hotspots for your javadoc parameters.

[jnairb]

I like the hotspots, so I think I'll keep them turned on, but I just wish I could automatically align them.

But I didn't realize I could edit the expansion. I noticed the \%u and \%v escapes and added \%u to the end of the @param line and now it seems to work like it did in v18. But I never created or edited these templates in the past, so something else must have changed in v19.

[patrick]

Yep, nothing changed on your end, there was a bug in a related fix that was making the parameter line still show up.  % \u makes it work again, but it should't be necessary in this case.  Once rc5 comes out, it should work correctly with or without the %\u.

[jnairb]

Thanks. It does work for me now without adding the %\u with 19.0.2 RC5.