At this point, the grid was just a list of lists. I first ignored Pygame, and created all the rules for the grid so that I could "check" if the puzzle's solution was correct. It's soooo easy to get frustrated and ragequit when you're trying to do the mechanics of your game AND the graphical display at the same time.Įxample: I'm currently writing a puzzle software that allows you to create and solve a specific type of puzzle (with the hopes of adding different kinds of puzzles later). Once you have the basic mechanics of the game working, Pygame is there to help you display images to the screen, and then affect those images based on user input (mouse clicks, keyboard buttons, etc.). That is, no graphics, just text to the screen telling you what's happening. Though you're eventually going to want to move to Pygame, my suggestion would be to get all your functions working for a non-GUI setting first. The vast majority of what you're going to need to do is going to be back-end.stuff that the user doesn't see.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |