Hi,
I asked this before, but got no reply. Generating new documentation
in my projects I noticed the problem again, so here is the question
again.
Using 'makeskel' against a unit it generated this snippet.
--------------------- BEGIN --------------------------
<!-- enumeration type Visibility: default -->
<element name="TCriteriaType">
<short/>
<descr>
</descr>
<seealso>
</seealso>
</element>
--------------------- END --------------------------
Loading the relevant .xml file with LazDoc, it shows that this element
has been documented (icons in the treeview have the letter 'T' on
them). Actually, it shows that the whole unit has been fully
documented, but one can clearly see that in hasn't been documented at
all!
Changing that code snippet to the following solves the problem. It
seems that if the xml start/end node pair are split over two lines
LazDoc thinks it has documentation added. Is this a issue with LazDoc
interpretting the xml incorrectly, or is this a issue with 'makeskel'
generating the skeleton xml incorrectly.
So basically which one is to blame for this anomaly? Is a xml node
where the start/end tags appear on separate lines considered having
data or still considered being empty?
--------------------- BEGIN --------------------------
<!-- enumeration type Visibility: default -->
<element name="TCriteriaType">
<short/>
<descr></descr>
<seealso></seealso>
</element>
--------------------- END --------------------------
--
Graeme Geldenhuys
There's no place like S34° 03.168' E018° 49.342'
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
