These forums have been invaluable for me, in learning about features of DipTrace that were omitted from, or obscurely described in, the Tutorial document. That is not a criticism of the Tutorial, which is really quite good, but writing is like programming, and even the most careful writing will turn out to have gaps or other bugs.
What this is building up to is that when before a newer version of the Tutorial is released, the DipTrace staff should comb through the forums, incorporating
all of the lore for which people now search the forums. Of course, some questions that have arisen have been, appropriately, answered with one or another gentle form of
Code:
RTFM.
Most questions, though, have revealed ways in which the Tutorial is obscure, often because it assumed some strategic conceptualization that was not explicitly described. If any part of the Tutorial requires explanation in the forums, that's a bug in the Tutorial
When manuals were all on paper, there were reasons to be terse, but that's gone. Sometimes forum discussion has revealed that an issue could be described in two or more different ways, with one description clear to some readers and another to others. When that's the case, the Tutorial might include both explanations.
A new version of the Tutorial should be seen as successful only if thereafter a novice will have no reason to search older forum discussions.