Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2011-10

Linking to properties in fpdoc files

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Hans-Peter Diettrich

When I want to link the documentation of property getters and setters to the property documentation, how should this be done? (fpdoc 2.7.1)

The following snippet from controls.xml results in strange HTML: <!-- function Visibility: protected -->
<element name="TControl.GetCursor" link="TControl.Cursor"/> <element name="TControl.GetCursor.Result">
<short/>
</element>

In controls/index.html the short description of GetCursor is taken from Cursor, that's fine :-)

But the link looks like this:
<a href="../../test/controls/index.html">GetCursor</a> what certainly is not the expected target :-(

A tcontrol.getcursor.html is not created - this is what I want to achieve, but does it confuse fpdoc, so that it creates a bad replacement link into the index?

DoDi

Reply by email

Michael Van Canneyt
to Hans-Peter Diettrich
Hans-Peter Diettrich wrote 20 lines
When I want to link the documentation of property getters and setters to the property documentation, how should this be done? (fpdoc 2.7.1) The following snippet from controls.xml results in strange HTML: <!-- function Visibility: protected --> <element name="TControl.GetCursor" link="TControl.Cursor"/> <element name="TControl.GetCursor.Result"> <short/> </element> In controls/index.html the short description of GetCursor is taken from Cursor, that's fine :-) But the link looks like this: <a href="../../test/controls/index.html">GetCursor</a> what certainly is not the expected target :-( A tcontrol.getcursor.html is not created - this is what I want to achieve, but does it confuse fpdoc, so that it creates a bad replacement link into the index?

Hm. That should not happen. I will have to , please enter a bug report, so I do not forget this.

Michael.

Reply by email