| Re: Inheriting Properties (or something similar) in IDLDOC [message #83116 is a reply to message #80787] |
Wed, 06 February 2013 11:10   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On 2/6/13 7:42 AM, Tom Grydeland wrote:
> Basically, this looks good. I have a couple of issues:
>
> 1) Shadowed (or overridden) methods are listed. I would much prefer
> they weren't. Showing only the method that will be called makes
> browsing documentation much easier. In the currently produced
> documentation, you have to look through the complete method list to
> see which one will be called. (And are superclasses listed in
> inheritance order or not?) Granted, there are tasks where knowing
> about the shadowed methods of superclasses is useful, but I would
> prefer a different approach. For instance, the documentation for
> each method could have a small box (beneath the signature, before
> documentation) stating "Overrides definition from superclass
> idl_object", with link to the documentation for the superclass method
> (when applicable).
>
> 2) In the top-level listing (frames view), I followed "subclasses"
> links from idl_object__define to mg_graph_democlass__define. From
> this window, links to inherited methods did not work.
> (HREF=" http://docs.idldev.com/mglib/vis/objects/idl_object__define. html#idl_object::init#idl_object::init")
Ok, I have a fix for 2), its in the git repo now and the online docs
will be updated shortly.
1) will take a bit more thought.
Mike
--
Michael Galloy
www.michaelgalloy.com
Modern IDL: A Guide to IDL Programming (http://modernidl.idldev.com)
Research Mathematician
Tech-X Corporation
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
