StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11146166
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-06-21T20:24:09.483
FavoriteCount
0
LastActivityDate
2012-06-21T20:24:09.483
LastEditDate
LastEditorUserId
0
OwnerUserId
97385
ParentId
11065708
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
(I'm the author of <a href="http://www.atomineerutils.com/" rel="nofollow">Atomineer Pro Documentation</a>) In Visual Studio, <ul> <li>Go to Tools > Atomineer > Atomineer Options... </li> <li>Switch to the "Advanced Customisation" tab </li> <li>Click the Block Templates - Doxygen button. </li> </ul> An editor (Notepad) will be opened containing the templates for you to customise. The templates are XML-based, and they dictate to Atomineer: <ul> <li>Which entries are legal (required or optional). Any entries not mentioned are considered "illegal" and deleted as you have found.</li> <li>The order in which entries should be sorted when comments are generated/updated</li> <li>Where to put additional whitespace (blank lines) in the comment blocks</li> <li>A few other things like whether punctuation correction should be enabled/disabled for each entry etc</li> </ul> There is a template for each different type of code element Atomineer can document, so you can get quite fine control of exactly how every part of your documentation looks, but it does mean you will have to copy and paste your new elements into each of the templates. For example, here is the default template for a Doxygen method comment: <pre><code> <method> <prototype _punctuate="false" /> <_ /> <summary /> <_ /> <author _punctuate="false">%user%</author> <date _punctuate="false">%date%</date> <_ /> <exception /> <_ /> <param /> <_ /> <returns /> <_ /> <sa _punctuate="false" _optional="true" /> </method> </code></pre> Each XML element (line) in this describes one entry in the comment. e.g. The XML tag <code><param/></code> corresponds to where the <code>@param</code> entries will be placed in the final comment block. The special element <code><_/></code> is used to indicate where blank lines should be inserted. (prototype is a special doxygen one, telling it where to insert the prototype/declaration @fn, @class, etc) To allow <code>@ingroup</code> and <code>@remarks</code> to be inserted into Atomineer comments, just add entries for them in the positions you want it to appear in the comment, like this: <pre><code> <method> <prototype _punctuate="false" /> <ingroup _optional="true" /> <_ /> <summary /> <_ /> <remarks _optional="true" /> <_ /> <author _punctuate="false">%user%</author> ... </method> </code></pre> You will see that the example elements I've added have the attribute <code>_optional="true"</code> in them. Without this, Atomineer will add the entry to every comment (a required entry). If it is set to <code>true</code>, then the entry will not be added by Atomineer, but if you type it in yourself, Atomineer will make sure to preserve it when you update a doc-comment. I apologise for how involved this is, but it's a flexible system that allows everybody to get what they want, albeit sometimes requiring a few minutes of setting up. Whenever I get time I am writing improved configuration tools and tutorials to make this process easier. Once you've configured it, though, you should have many happy years ahead ;-) There is more documentation on Templates and the other things you can do in them <a href="http://www.atomineerutils.com/rulesguide.php" rel="nofollow">here</a>. If you have further questions, feel free to drop a line to the support email, which is at the bottom of every page on the Atomineer website. I'm always happy to help.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POModifying rules in Atomineer
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJason Williams
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POModifying rules in Atomineer
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COWow! Thanks! That's exactly what I was looking for.
 singulars
 PostPostId
 PO
 UserUserId
 USBryan C.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.