Fixed doxygen comments.

This commit is contained in:
Robert Osfield
2005-05-20 21:01:57 +00:00
parent 57d333fd0f
commit b8b6ed8e34
8 changed files with 28 additions and 27 deletions

View File

@@ -26,9 +26,9 @@
namespace osgParticle
{
/** An operator that applies a constant force to the particles.
Remember that if the mass of particles is expressed in <U>kg</U> and the lengths are
expressed in <U>meters</U>, then the force should be expressed in <U>Newtons</U>.
/** An operator that applies a constant force to the particles.
* Remember that if the mass of particles is expressed in kg and the lengths are
* expressed in meters, then the force should be expressed in Newtons.
*/
class ForceOperator: public Operator {
public:

View File

@@ -29,11 +29,11 @@
namespace osgParticle
{
/** A common base interface for those classes which need to do something on particles. Such classes
are, for example, <CODE>Emitter</CODE> (particle generation) and <CODE>Program</CODE> (particle animation).
This class holds some properties, like a <I>reference frame</I> and a reference to a <CODE>ParticleSystem<CODE>;
descendant classes should process the particles taking into account the reference frame, computing the right
transformations when needed.
/** A common base interface for those classes which need to do something on particles. Such classes
* are, for example, Emitter (particle generation) and Program (particle animation).
* This class holds some properties, like a <I>reference frame</I> and a reference to a ParticleSystem;
* descendant classes should process the particles taking into account the reference frame, computing the right
* transformations when needed.
*/
class OSGPARTICLE_EXPORT ParticleProcessor: public osg::Node {
public:

View File

@@ -33,11 +33,11 @@
namespace osgParticle
{
/** The heart of this class library; its purpose is to hold a set of particles and manage particle creation, update, rendering and destruction.
You can add this drawable to any <CODE>Geode</CODE> as you usually do with other
<CODE>Drawable</CODE> classes. Each instance of <CODE>ParticleSystem</CODE> is a separate set of
particles; it provides the interface for creating particles and iterating
through them (see the <CODE>Emitter</CODE> and <CODE>Program</CODE> classes).
/** The heart of this class library; its purpose is to hold a set of particles and manage particle creation, update, rendering and destruction.
* You can add this drawable to any Geode as you usually do with other
* Drawable classes. Each instance of ParticleSystem is a separate set of
* particles; it provides the interface for creating particles and iterating
* through them (see the Emitter and Program classes).
*/
class OSGPARTICLE_EXPORT ParticleSystem: public osg::Drawable {
public:
@@ -87,9 +87,9 @@ namespace osgParticle
/** Set the double pass rendering flag.
Double pass rendering avoids overdraw problems between particle systems
and other opaque objects. If you can render all the particle systems <U>after</U>
and other opaque objects. If you can render all the particle systems after
the opaque objects, then double pass is not necessary and can be turned off (best choice).
If you set the default attributes with <CODE>setDefaultAttributes</CODE>, then the particle
If you set the default attributes with setDefaultAttributes, then the particle
system will fall into a transparent bin.
*/
inline void setDoublePassRendering(bool v);

View File

@@ -32,9 +32,9 @@ namespace osgParticle
{
/** A useful node class for updating particle systems automatically.
When a <CODE>ParticleSystemUpdater</CODE> is traversed by a cull visitor, it calls the
<CODE>update()</CODE> method on the specified particle systems. You should place this updater
<U>AFTER</U> other nodes like emitters and programs.
When a ParticleSystemUpdater is traversed by a cull visitor, it calls the
update() method on the specified particle systems. You should place this updater
AFTER other nodes like emitters and programs.
*/
class OSGPARTICLE_EXPORT ParticleSystemUpdater: public osg::Node {
public: