It looks like FPDoc links to an inherited item (method), when only a short description is provided for an overridden method. Is this intended behaviour? (see Controls.TDragControlObject)

The short description is shown e.g. in the class declaration, but the link from there goes to the inherited method. What's required that links go to the overridden method description instead?

Please note that I don't ask for an change of this behaviour, only for a confirmation whether this is reliable behaviour (by design).

DoDi

It looks like FPDoc links to an inherited item (method), when only a short description is provided for an overridden method. Is this intended behaviour? (see Controls.TDragControlObject)

I also have the impression that FPDoc does not (always) overwrite existing HTML files.

DoDi

Thanks for the improvements in the last updates, but...

How do I obtain the latest documentation on FPDoc?

For records with variant parts, no short descriptions are shown for the members in the variant part. Parameters for overloaded methods are already supported, so this extension should not be too hard to implement?

FPDoc now also doesn't have "html" as the default format, requires an explicit format parameter.

The handling of the css file still is cryptic. Even with --css-file given no file is copied. The location seems to have changed to the parent directory, i.e. docs/html?

The messages have changed.
What does it mean, when a dependency(?) could not be resolved? (heritage, link, ???)
When heritage is meant, I'd suggest something like "Ancestor ... of ... not found". At least I like messages starting with a fixed part, indicating the message type, not with an identifier.

What do the "new alias ..." messages mean *to the user*?

DoDi

Hans-Peter Diettrich wrote

Thanks for the improvements in the last updates, but... How do I obtain the latest documentation on FPDoc?

make fpdoc.pdf in docs.

For records with variant parts, no short descriptions are shown for the members in the variant part. Parameters for overloaded methods are already supported, so this extension should not be too hard to implement?

Well, in that case presumably you can handle it ?

FPDoc now also doesn't have "html" as the default format, requires an explicit format parameter.

This behaviour has not changed recently.

The handling of the css file still is cryptic. Even with --css-file given no file is copied. The location seems to have changed to the parent directory, i.e. docs/html?

This behaviour has not changed recently.

The messages have changed. What does it mean, when a dependency(?) could not be resolved? (heritage, link, ???)

Presumably a class inheritance. Can you post a more clear message ?

None of the messages have changed the last 8 months. I checked this.

You may now get extra messages since you use it more (or better), but not changes.

As far as I can tell, they are debug messages.

Michael.

In our previous episode, Michael Van Canneyt said:

I commented those. Some other alias msgs are still there, but they really indicate problems, while these were mostly to follow flow (or at least only signaled problems after manual analysis of the output).

If you find such errors relating to preoceduretypes, please leave them in. They are in spots that have something to do with the remaining fpdoc crash (when compiling lcl if fpdoc is compiled without -O-)

I use them to see if tracebacks that I get back are the same as the ones I get myself.

> How do I obtain the latest documentation on FPDoc? make fpdoc.pdf in docs.

No Latex support here (Win7)

I'm a user of fpdoc, not a maintainer, have no idea of the internals.

> FPDoc now also doesn't have "html" as the default format, requires an > explicit format parameter. This behaviour has not changed recently.

Well, it's documented as the default, and was working so in some older version. I've fpdoc 2.2.4 in my path by default...

new alias #rtl.System.IInterface (IUnknown)
new alias #rtl.System.IInterface (IUnknown)
new alias #rtl.System.IInterface (IUnknown)
TCustomActionList's dependency TLCLComponent could not be resolved TArrow's dependency TCustomControl could not be resolved TAsyncProcess's dependency TProcessUTF8 could not be resolved ...

> What do the "new alias ..." messages mean *to the user*? As far as I can tell, they are debug messages.

How to turn off?

DoDi

Then no more recent docs than the official ones on the website.

In that case, please do not say things like
'this extension should not be too hard to implement' But please, file a bug report so we won't forget.

2.2.4 ? That is definitely not 'recently' :-)

It refers to a parent class. I've adapted the message to be more clear.

Comment out in code. I think Marco took care of it already.

Michael.

This whole threads is about bugs and problems with FPDoc, in the hope that most can be fixed without extra bug reports.

Thanks :-)

DoDi

If I ask you to add this as a bug report it is because a) I indeed consider it a bug
b) I realize it is not fixable in 10 minutes and hence will not be done anytime soon.

Michael.

Hans-Peter Diettrich wrote

No Latex support here (Win7)

Virtual Box is your friend :-) .

-Michael

Michael Schnell wrote

On 09/11/2011 07:33 PM, Hans-Peter Diettrich wrote: > No Latex support here (Win7) Virtual Box is your friend :-) .

Even easier, you get LaTeX for Windows too... I think it is called something like MiKTex.

Regards,
- Graeme -

In our previous episode, Graeme Geldenhuys said:

>> No Latex support here (Win7) > Virtual Box is your friend :-) . Even easier, you get LaTeX for Windows too... I think it is called something like MiKTex.

Even better, TeXLive has easy installers nowaday, and that is the TeX distro mostly used on *nix.

I tried and it works if you do one manual at the time, but have to comment some unix shell script in Makefile.4ht which moves the generated files to a directory.