We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PozaziemscyZaborcy/main_game.py
Line 5 in 428434b
PozaziemscyZaborcy/main.py
Line 6 in 428434b
As you can see, you initialize pygame two times. But it isn't the only issue.
In main_game.py you have a bunch (rather, a fucking ton) of references to Game object and implement all the methods there.
main_game.py
Game
I can see that this decoupling of structure/behaviour is used in C++. But this isn't C++.
IMHO just move all the methods to game.py where they belong and instantiate Game object in main.py.
game.py
main.py
If you have any questions, feel free to ask.
The text was updated successfully, but these errors were encountered:
we we pal gume spoko jest
Sorry, something went wrong.
No branches or pull requests
PozaziemscyZaborcy/main_game.py
Line 5 in 428434b
PozaziemscyZaborcy/main.py
Line 6 in 428434b
As you can see, you initialize pygame two times. But it isn't the only issue.
In
main_game.py
you have a bunch (rather, a fucking ton) of references toGame
object and implement all the methods there.I can see that this decoupling of structure/behaviour is used in C++.
But this isn't C++.
What you need to do
IMHO just move all the methods to
game.py
where they belong and instantiateGame
object inmain.py
.If you have any questions, feel free to ask.
The text was updated successfully, but these errors were encountered: