Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Ignore:
Timestamp:
Sep 9, 2015, 4:10:21 PM (9 years ago)
Author:
landauf
Message:

removed the 'bAddRef' argument from StrongPtr's constructor. it was a bad hack and shouldn't be used. in fact, it was only used to avoid recursive dependencies if one of the four base objects (Namespace, Level, Gametype, Scene) referenced itself with a StrongPtr.
instead of the 'bAddRef'-hack BaseObject now stores the references in a new construct called StrongOrWeakPtr which can either store the reference in a StrongPtr (like it did before) or in a WeakPtr (which is a cleaner alternative to 'bAddRef=true')

File:
1 edited

Legend:

Unmodified
Added
Removed
  • code/branches/core7/src/orxonox/Level.cc

    r10576 r10578  
    4949        RegisterObject(Level);
    5050
    51         this->setLevel(StrongPtr<Level>(this, false));
     51        this->setLevel(WeakPtr<Level>(this)); // store a weak-pointer to itself (a strong-pointer would create a recursive dependency)
    5252
    5353        this->registerVariables();
     
    123123        Gametype* rootgametype = orxonox_cast<Gametype*>(identifier->fabricate(this));
    124124
    125         rootgametype->setLevel(NULL); // avoid circular references
    126         this->setGametype(rootgametype);
     125        rootgametype->setLevel(StrongPtr<Level>(NULL)); // avoid circular references
     126        this->setGametype(StrongPtr<Gametype>(rootgametype));
    127127        rootgametype->init(); // call init() AFTER the gametype was set
    128128
Note: See TracChangeset for help on using the changeset viewer.