Thought I might share this with everyone even though I really don't know what it means or how to take full advantage of it.
A:M Answers stores text in a local file named AMAIndex.txt which is in your Hash Inc installation folder.
This file can be edited from within A:M by opening any Property and editing the Properties Documentation panel.
For the most part we are limited to those Properties that are hard coded into A:M.
But can we write custom properties?
In a Model we can create Named Groups on any geometry and within those named Groups we can create Properties.
There are three kinds of properties we can create (Folders, Percentages and On/Off).
We can not only edit the A:M Answers Property Description for these properties but we can also edit the title by changing the name of the Folder, Percentage or On/Off Title.
Now here's where it gets weird...
Let's say you have two Models that are exactly the same (except small trivial differences that won't interfere with what I'm about to describe).
If you open either and go to the A:MA documented property you will see the original documentation.
If you edit one you can update the other by refreshing it via a Right Click and selecting 'Display Help for Current Property'.
As this is an undocumented feature there is no guarantee that it will be there in the future. However, there are some interesting things going on here.
I've described the lead up to it and if interested you can now dive into it.
What does it all mean.
Primarily, it gives us a way to document our Model's Properties (or more accurately our Named Group properties within the Model).
But note that this type of documentation does not stay with the model. It has a record saved in the A:MA index and to the best of my knowledge these documentations don't disappear automatically.
For instance, in the case of the two identical Models above, if I were to edit a Named Group property and change it's title name then open it in the other model and change it again I would create a new A:MA entry for that same named property. The assumption here is that A:M will retain all but only show the most recently updated property. If this is true we may be seeing a form of a journal in the making or means to share information with others simultaneously. All it would take is knowing the right property title and updating our view of the A:MA property.
Big Brother? No, I could only wish we had that level of technology.
But this is at least one way we can currently add customized A:MA property documentation.
And if we share our AMAIndex.txt and appropriate Model/Project we'll have also shared that documentation.
Disclaimer: Using undocumented features, or even unofficially undocumented features, can lead to frustration when that feature is updated, removed or altered. As always, use undocumented features cautiously.