Abstract class defining the interface to be implemented by particle affectors.
More...
#include <OgreParticleAffector.h>
|
| static void | cleanupDictionary () |
| | Cleans up the static 'msDictionary' required to reset Ogre, otherwise the containers are left with invalid pointers, which will lead to a crash as soon as one of the ResourceManager implementers (e.g.
|
Abstract class defining the interface to be implemented by particle affectors.
- Because there are so many types of affectors you could use, OGRE chooses not to dictate the available types. It comes with some in-built, but allows plugins or applications to extend the affector types available. This is done by subclassing ParticleAffector to have the appropriate emission behaviour you want, and also creating a subclass of ParticleAffectorFactory which is responsible for creating instances of your new affector type. You register this factory with the ParticleSystemManager using addAffectorFactory, and from then on affectors of this type can be created either from code or through text particle scripts by naming the type.
- This same approach is used for ParticleEmitters (which are the source of particles in a system). This means that OGRE is particularly flexible when it comes to creating particle system effects, with literally infinite combinations of affector and affector types, and parameters within those types.
◆ ParticleAffector()
◆ ~ParticleAffector()
| virtual Ogre::ParticleAffector::~ParticleAffector |
( |
| ) |
|
|
virtual |
Virtual destructor essential.
◆ _initParticle()
| virtual void Ogre::ParticleAffector::_initParticle |
( |
Particle * | pParticle | ) |
|
|
inlinevirtual |
◆ _affectParticles()
| virtual void Ogre::ParticleAffector::_affectParticles |
( |
ParticleSystem * | pSystem, |
|
|
Real | timeElapsed ) |
|
pure virtual |
◆ getType()
| const String & Ogre::ParticleAffector::getType |
( |
void | | ) |
const |
|
inline |
Returns the name of the type of affector.
The documentation for this class was generated from the following file: