| commit | 38642b610013624f07d4836a0ed1d9c00a2699b4 | |
| author | rustushki <rustushki> | |
| Mon, 4 Dec 2006 04:11:09 +0000 (4 04:11 +0000) | ||
| committer | rustushki <rustushki> | |
| Mon, 4 Dec 2006 04:11:09 +0000 (4 04:11 +0000) | ||
| tree | 14af85dd0c33a3c5c49dda320476fa31f31dc786 | treesnapshot (tar.gz zip) |
| parent | 10113114f87e334611c23e13832533892d599a42 | commitdiff |
Sean: realized we needed to update the constructor def. (my fault; sorry)
Explanation:
If Screen is a Surface, and BattleScreen is a Screen, and if Asgard instantiates and owns the Surface that is the displayed window then:
The program would have to write all 800*600 pixels twice. (which is bad) Once to the BattleScreen, and then once again to the actual display that the user sees.
Now the display Surface is passed to BattleScreen.__init__(..), which it then uses to instantiate Screen. Screen takes that same Surface object and becomes it. I.e., the Surface is passed in as Screen.__init__()'s "self" parameter. Very confusing, and I should have caught it earlier.
Explanation:
If Screen is a Surface, and BattleScreen is a Screen, and if Asgard instantiates and owns the Surface that is the displayed window then:
The program would have to write all 800*600 pixels twice. (which is bad) Once to the BattleScreen, and then once again to the actual display that the user sees.
Now the display Surface is passed to BattleScreen.__init__(..), which it then uses to instantiate Screen. Screen takes that same Surface object and becomes it. I.e., the Surface is passed in as Screen.__init__()'s "self" parameter. Very confusing, and I should have caught it earlier.
| asgard.py | diffblobblamehistory | |
| screen.py | diffblobblamehistory |