Changes between Version 1 and Version 2 of SceneLoop


Ignore:
Timestamp:
02/26/08 10:22:05 (6 years ago)
Author:
ArcRiley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SceneLoop

    v1 v2  
    22== where we process physics == 
    33 
    4 '''!SceneLoop''' is the thread that calls each Scene object to process it's physics in the background.  This allows physics to remain realtime regardless of rendering (in WindowLoop) or the Python code being processed in the main thread. 
     4'''!SceneLoop''' is the instance of '''soy._internals.!LoopThread''' which calls each instance of '''soy.scenes.Scene''' to process it's physics in the background.  This allows physics to remain real-time regardless of rendering (processed in WindowLoop) or the Python code being processed in the main thread. 
    55 
    6 To avoid frequent Scene locking ODE calls should be isolated to this thread.  When ODE calls must exist outside this thread the Scene's stepLock() must be called and, with as little processing as possible, that Scene object's stepUnlock() should be called.  Access to any dBody or dGeom without it's Scene's lock will inevitably cause problems for some users. 
     6To avoid frequent scene locking ODE calls should be isolated to this thread.  When ODE calls must exist outside this thread the scene's stepLock() must be called and, with as little processing as possible, that scene object's stepUnlock() should be called.  Access to any dBody or dGeom without it's scene's lock will inevitably cause problems for some users. 
    77 
    88'''!SceneLoop''' replaced this function of CoreLoop with [954]