Am I crazy, or do the new docs not list parent classes?

[Thom_McGrath]

Look at DesktopButton — Xojo documentation

The page doesn’t contain DesktopUIButton at all. None of the pages appear to reference the parent classes. That’s quite an oversight.

What I was actually looking for was the parent class to DesktopContainer, as it doesn’t appear to be DesktopWindow. The old docs tell me that yes, it is, but that’s odd because DesktopContainer is missing things that exist on DesktopWindow.

But still, back to my original point, how does somebody write developer docs without including the parent class?

[Tim_Hare]

At the bottom of that page, it lists the parent as DesktopUIControl. Is that wrong?

[Thom_McGrath]

Nope, not wrong. I am crazy. I searched the page originally and found no matches. Now there are 9, so I must have made a typo.

[Rick_Araujo]

Anyway, the control inheritance (or at least its direct ascendant, parent class) shouldn’t be a footnote, if possible.

Take for example .Net, all the base class definition is listed before the class details, as constructors, properties, methods, etc. Not in a “See Also” footnote.

Then the rest comes…

[Julia_Truchsess]

Or the old Xojo docs

[Tim_Hare]

At least they put it in a consistent place.

[DerkJ]

This is a good way to show how the inherhitance walks the tree.

[Rick_Araujo]

@Tim_Hare

At least they put it in a consistent place.

Negative points to the fact of it being hidden, and where no one expects to find it. “See Also”?

Better just add one simple line: