• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
K1NNY

Trouble with importing my own modules

7 posts in this topic

I have three files: Main.py, Game.py, and CreateDisplay.py . Obviously Main is going to be the main file where everything is going to run from. This is my first project that i have split the code into separate modules and i am having problems.

 

The problem i am having is that when the display is made, the background isn't filled with white, its black, and no matter what i do to the variable 'WHITE' it stays black.

 

Here is the code for each:

 

Main.py

import pygame
import sys
import Game
import CreateDisplay

#####the main file#####

pygame.init()

if __name__ == '__main__':


    Game.Main()

    for event in pygame.event.get():
        
        if event.type == pygame.QUIT:
            pygame.quit()
            sys.exit()

    pygame.display.update()

 

 

Game.py

 

import pygame
import sys
import CreateDisplay

#####the real main game file#####

pygame.init()    


def Main():

    while True:

        CreateDisplay.Display()


        for event in pygame.event.get():
            if event.type == pygame.QUIT:
                pygame.quit()
                sys.exit()

 

 

CreateDisplay.py

 

import pygame
import sys

#####this is the file to make the screen#####

pygame.init()

def Display():

    WHITE = (255, 255, 255)

    DISPLAY = pygame.display.set_mode((1024, 720))

 

Please help! I can't figure out what is wrong and i've been working with it for about an hour.

0

Share this post


Link to post
Share on other sites

Why are you importing CreateDisplay into Main.py? You are not using it. Anyway, I suspect the problem is you are trying to use python modules like C++ headers. You import pygame three times, once in each file. Each file will have a separate, distinct pygame object (or whatever it is). What you should do is create your stuff in the main script, and pass it to the other scripts. But for simplicity I suggest you stick to a single file for now.

0

Share this post


Link to post
Share on other sites

Why are you importing CreateDisplay into Main.py? You are not using it. Anyway, I suspect the problem is you are trying to use python modules like C++ headers. You import pygame three times, once in each file. Each file will have a separate, distinct pygame object (or whatever it is). What you should do is create your stuff in the main script, and pass it to the other scripts. But for simplicity I suggest you stick to a single file for now.

 

I've made many programs using one file and am doing my new project this way to learn how to properly do it. So I should only import pygame in Main.py?

0

Share this post


Link to post
Share on other sites

You are not using the variable WHITE anywhere though. If you want the surface to be white, you have to call fill on DISPLAY, then call flip.

 

Each file will have a separate, distinct pygame object (or whatever it is).

 

I think multiple imports of the same module will only have the effect of one import. The first will add the module object to a dict, and any other times it will just do a look up.

Edited by ultramailman
2

Share this post


Link to post
Share on other sites

What is the error message?

Also, why are you calling pygame.init() in every file?

 

You should rethink the way your game is made, you have unreachable codes and very, very confusing names.

When you have a main and a real main there is definitely something wrong with your code.

0

Share this post


Link to post
Share on other sites

As ultramailman mentioned, you initialized "WHITE" but never used it anywhere. The value is correct for a true white color, it just comes down to setting the color of the screen. 

 

 

 

screen.fill(WHITE); 
 

 

 

and after that you are going to want to make sure that you use pygame's flip method to properly display the screen. 

 

 

 

pygame.display.flip();
 

 

0

Share this post


Link to post
Share on other sites

As ultramailman mentioned, you initialized "WHITE" but never used it anywhere. The value is correct for a true white color, it just comes down to setting the color of the screen. 

 

 

 

screen.fill(WHITE); 
 

 

 

and after that you are going to want to make sure that you use pygame's flip method to properly display the screen. 

 

 

 

pygame.display.flip();
 

 

I'm not sure why it isn't in the code sections above but i called for "DISPLAY" to be filled "WHITE" and it is not working. I combined CreateDisplay.py and Game.py, and added pygame.diplsay.flip() to the Game() definition and it works fine now. I assumed having pygame.display.update() in Main.py would be enough.

0

Share this post


Link to post
Share on other sites



I've made many programs using one file and am doing my new project this way to learn how to properly do it.

 

Sometimes using one file is the proper way to do it, depending on how you are structuring the code. How complex your game is would also have a big impact on how the code is layed out. As Bacterius mentioned, you are using Python modules like C++ headers. Try and treat modules like their name implies for a "modular" design. A google search for "python idioms" may yield some useful information.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0