• 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.

Archived

This topic is now archived and is closed to further replies.

mmcconnell

OO Game Design

7 posts in this topic

I wouldn't say that is a OO problem.

You should just pass the right parameters (ie, the surface) to the function which draws the sprite.....

That's what I would do

------------------
Dance with me......

0

Share this post


Link to post
Share on other sites
The way I handled this was by splitting it into a bunch of layers:

1 - DirectDraw. Just blits in DX and inits DX.
2 - Blitting. Abstraction for blitting, so its API/OS independent.
3 - Draw Queue. Makes a queue that can add/clear list of things to draw. Can draw images, text, animations, etc.
4 - Elements, like sprites and text. These can each have things like sprite->Draw(). text->Draw(). Which will create an index in the DrawQueue...

-Geoff

0

Share this post


Link to post
Share on other sites
Hi !

Well, some people will tell me I am stupid, but I would create a global instance of class DrawManager.
Define this global variable somewhere in your main.cpp or winmain.cpp or something like that like so:

DrawManager MyDrawManager;

In your main.h or winmain.h or something like that put in a:

extern DrawManager MyDrawManager;

Well, that's all. Now you have access to MyDrawManager from everywhere in your program (you will have to include main.h into the implementation file of sprite. Then you could do something like that:

.....
#include "main.h"

void Sprite: raw(long x, long y)
{
MyDrawManager.DrawSprite(this,x,y);
}

Too many global variables are shit, but a few of them are great, cause you have access to them everywhere without casting pointers around all over the time. Pointers are dangerous cause they cause a GPF when they are NULL, and checking them all the time is shit, too !!

Hope this helps.

Phillip

0

Share this post


Link to post
Share on other sites
There are many ways to skin this cat. I am using a similar system in my Project at work: I have touch screen buttons, animating images, updating text areas, etc....all making up my game screen...and each able to change at any time. So what I have is an abstract base class (Image) which contains the Redraw() method. During initialization I add each the screen elements to a list of Image pointers (in addition to the other LOGICAL places it needs to be), then each frame (as called by a timer) I traverse the list calling the Redraw() function for each element. Each element's class can implement the ability to only actually blit if the image has changed...but beware, if you double(triple) buffer they need to set a conuter when they change...and decrament it each flip...so they can get the new version onto each buffer.

Now you see that the Instantiating classes needs to know details of the DisplayManager (like what buffering, unless you blit all of them EVERY frame)...so I recommend one of the following....global variable or static class memeber (IF you do not intend to support multiple monitor or video card setups)..otherwise you might need to pass the DisplayManager to each of the redraw functions...this way additional monitors can be added by just making TWO seperate Image lists...each one associated with a particular DisplayManager.

I could send you source or look at your source if you'd like.

0

Share this post


Link to post
Share on other sites
What yo are asking is basicaly how to use classes, if yo need another class to access variables in another one jus go like this:

class Game {
int score;
public:
int Give_Score(){return score;}
void Change_Score(int score1){score=score1;}
};

Then if yo need to print score jus do :
printf("WHATEVER:%s",Game.Give_Score());

and yo no how to change score

I think thatl work

0

Share this post


Link to post
Share on other sites
Esap1: First, your use of English made that posting a little cryptic, but the question is not how to use classes but a specific problem that, unfortunately, has nothing really to do with access control functions in a class. What you described is in fact a solution to a common problem with classes (controlled access to almost-public variables) but is not the problem we are dealing with here.

- Splat

0

Share this post


Link to post
Share on other sites
I'm looking for some suggestions on Object Oriented game design. I'm new to C++ so this might seem like a simple question. I've got a DrawManager class that wraps DirectX, I've also got a Sprite Class. Here's the problem. I want my sprite class to be able to draw itself sprite->Draw(). The main game also needs access to the DrawManager to display things like score. How do I let the sprite class have access to the DrawManager?

Marcus

0

Share this post


Link to post
Share on other sites
Sorry Splat if I did not fully understand the question, and also, I really dont think that I write very bad . I have to admit, Im no teacher But I do have experience in programming games and made a few and must of just mis understood his question, as I am new to DX. sorry.
0

Share this post


Link to post
Share on other sites