Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate
summaryrefslogtreecommitdiffstats
path: root/MAFH2/BattleEngine.py
diff options
context:
space:
mode:
authorjlew <jlew.blackout@gmail.com>2010-06-28 21:52:40 (GMT)
committer jlew <jlew.blackout@gmail.com>2010-06-28 21:52:40 (GMT)
commit721d43756cf45596a2968ae9e01c3c0357b73a07 (patch)
tree07d80032238964f17104aff83cba8d0089bce06f /MAFH2/BattleEngine.py
parentbf007b892cd8e2aaf6f9a565ae3f166e53716501 (diff)
Added a lock over the draw and event loops (ticket #29)
There is an issue that changing values from the event loop while in mid draw can cause some crazy frames until the next static frame is drawn. So this commit adds a lock over the even loops and the draw loops that prevents python from stealing the thread while drawing or modifying internal variables that are used by the drawing methods. Question: Should I instead implement a game engine locking system so that the event can lock only on its drawing portion or leave it over the entire draw/update process.
Diffstat (limited to 'MAFH2/BattleEngine.py')
0 files changed, 0 insertions, 0 deletions