Re: Qt Properties
Matthias Kretz <[email protected]>
| Newsgroups | gmane.text.doxygen.devel |
|---|---|
| Organization | Kretz |
| Message-ID | <[email protected]> |
Hi again,
I give up without a helping hand. Too many of the methods are not documented
and I have to read to code only to figure out that they're not doing what I'm
looking for. :-(
I made doxygen write "Access function: " + getReadAccessor() +
getWriteAccessor() in the property docs, but after about one day of reading
doxygen source I had hoped to get further.
If somebody can guide me on IRC I'm Vir on freenode or just reply to this
list. I'm subscribed.
Good night,
Matthias
On Wednesday 22 March 2006 22:49, Matthias Kretz wrote:
> Hi,
>
> while documenting properties for the upcoming KDE4 API I noticed that
> documenting Q_PROPERTY macros partially works. But there's a few things I'd
> like to fix if you can tell me where to look:
>
> 1. The HTML documentation doesn't specify what the ReadAccessor and
> WriteAccessor are. I like the way it is done for Qt (look at
> http://doc.trolltech.com/4.1/qaction.html#checked-prop ).
>
> So I'd like to add the necessary code to write out "Access function:\n - "
> + getReadAccessor() + "\n - " + getWriteAccessor()
> Where do I have to look (apparently the accessor functions are written into
> the XML output, but not the HTML output)?
>
> 2. If the accessor functions are undocumented doxygen currently gives a
> warning. Ideally doxygen should see that the documentation is not needed
> anymore and link the functions from the index to the property documentation
> and not give any warnings - to the contrary it should give a warning if the
> property and the accessors are documented.
> Is this possible? Where?
--
C'ya
Matthias
________________________________________________________
Matthias Kretz (Germany) <><
http://Vir.homelinux.org/
[email protected], [email protected],
[email protected]
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBELFLgyg4WnCj6OIoRApblAKDowQc9UPIFZKlG5QpyEYczIIzFkACcChhZ ff51J70INp35uNR285gRmwE= =VSt9 -----END PGP SIGNATURE-----