Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Ignore:
Timestamp:
Jan 1, 2009, 7:34:44 PM (15 years ago)
Author:
rgrieder
Message:
  • Added WorldEntityCollisionShape to clarify when a CompoundCollisionShape belongs to a WE.
  • Also fixed problems with the synchronisation of the CollisionShape hierarchy.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • code/branches/presentation/src/orxonox/objects/worldentities/WorldEntity.h

    r2540 r2562  
    4343#include "core/BaseObject.h"
    4444#include "network/synchronisable/Synchronisable.h"
    45 #include "objects/collisionshapes/CompoundCollisionShape.h"
    4645
    4746namespace orxonox
     
    6968        You can get more information at the corresponding set function.
    7069
    71         Collision shapes: These are controlled by the internal CompoundCollisionShape. @see CompoundCollisionShape.
     70        Collision shapes: These are controlled by the internal WorldEntityCollisionShape. @see WorldEntityCollisionShape.
    7271    */
    7372    class _OrxonoxExport WorldEntity : public BaseObject, public Synchronisable, public btMotionState
     
    399398            //! When attaching objects hierarchically this variable tells this object (as child) whether physics was activated before attaching (because the deactivate physics while being attached).
    400399            bool                         bPhysicsActiveBeforeAttaching_;
    401             CompoundCollisionShape       collisionShape_;                //!< Attached collision shapes go here
     400            WorldEntityCollisionShape*   collisionShape_;                //!< Attached collision shapes go here
    402401            btScalar                     mass_;                          //!< @see setMass
    403402            btVector3                    localInertia_;                  //!< @see getLocalInertia
Note: See TracChangeset for help on using the changeset viewer.