Angus Leeming <[EMAIL PROTECTED]> writes:
| Looks good. A few questions:
|
| This looks like a typo:
| > QAboutDialog::~QAboutDialog()
| > -{
| > -}
| > +{}
| > +y
| >
yes. fixed in my sources
| ?????:
| Index: src/frontends/qt2/QRefDialog.h
| - void refHighlighted(QString const &);
| - void refSelected(QString const &);
| + void refHighlighted(const QString &);
| + void refSelected(const QString &);
qt mumbo-jumbo. moc does not grok "Type const &" correctly at all
times, I am just making .h and .C agree to avoid doxygen warnings.
| Why?:
| Index: src/frontends/xforms/FormPrint.C
| +#include "support/lstrings.h"
once upon a time my compiler required that... perhaps not any more...
| I don't understand... When should \param be used and when \c?
| Index: src/frontends/xforms/combox.h
| /** The browser will be displayed either below or above the button,
| - * dependent upon \param position.
| + * dependent upon \c position.
\param is for documenting params, works like the 'description' envir
of latex.
\c makes the arg verbatim/fixed font.
\param was being used wrong, and still is in a lot of cases, I fixed
the onces creating doxygen warnings.
--
Lgb
