RE: [Doxygen-users] Re: Documenting enums of an IDL file

[Francois St-A. <fst...@do...>]

Don,

First, sorry about the HTML; it's out of my control. I *am* writing =
this in
plain text, but it will most certainly be transformed to HTML by our
Exchange Server (I have informed our Admins, but they are not always =
quick
to act on such "details"...)

Well, I'm glad you are having success. It is encouraging, because it =
tells
me that it can be done! However, it's frustrating because I can't get =
it to
work myself. If only I had a complete example...

I have tried Doxygen 1.2.6 on my IDL file, but it didn't work. =
Therefore I
cannot yet blame this on a problem in the recent version. It must be =
because
I'm doing something wrong. I don't think it's my enum definition =
itself,
because simply moving my enums into an interface definition makes =
Doxygen
recognize them.

Perhaps it is generated but I don't see it? I have followed every HTML =
link,
but I never found it.  A "Something.idl File Reference" link? I don't =
see
this in my generated documentation.=20

Except for comments, my enum definition is the first thing in my IDL =
file.

I now strongly suspect either something is missing from my IDL or =
Doxyfile.

Fran=E7ois St-Arnaud.

> -----Original Message-----
> From: Don McClimans [mailto:dmc...@in...]
> Sent: Tuesday, February 19, 2002 5:26 PM
> To: dox...@li...
> Subject: [Doxygen-users] Re: Documenting enums of an IDL file
>=20
>=20
> Francois,
>=20
> First, I for one would appreciate it if you (and others)=20
> would not post HTML messages to the group.

<snip>

>=20
> Now, regarding enums in IDL. I have no problems getting=20
> Doxygen to generate
> documentation for global enums in an IDL file. This is in an=20
> ATL project, as
> well. However, I am still using Doxygen 1.2.6, because there's been =
no
> reason for me to upgrade. So perhaps it is a problem in newer=20
> versions? Or
> perhaps there is something slightly "wrong" (different) about=20
> your enum
> declaration? Or perhaps it is actually there but you haven't seen it
> (because it is with other global objects, not on an interface=20
> documentation
> page)?
>=20

<snip>

> This is before the first interface definition, not inside it, as you
> describe. Works fine. Because it's a global, the enum=20
> documentation shows up
> on the "Something.idl File Reference" page, but it's=20
> correctly hyper-linked
> where it's used, so that doesn't bother me much.
>=20
<snip>