Hi, all. I''m trying to get a simple 2D engine together to drive a few small game ideas I have and I''m having some doubts on my design (since this is the first time I try this sort of thing).
I would like to hear on how some of you manage objects within your game. I''ll post info on the way I''m thinking of doing it and if you see any flaws or a better way of doing it, please let me know.
Simple prite structure:
struct Sprite
{
SDL_Surface *texture;
int x;
int y;
int z;
int xvel;
int yvel;
int zvel;
int life;
bool invulnerable;
bool opaque;
};
Then i''m planning on having a class like the following:
class CObjectManager
{
public:
UpdatePosition();
SendToRenderer();
etc...();
private:
list SpriteList;
};
I think this would work fine if I updated all objects all the time, but how would I Identify and access an individual object within the game? Would it be better to have different object types for static things that don''t move?
If you have any ressources that speak on this subject please let me know.
--
Josh Boudreau
This isn''''t an office. It''''s Hell with fluorescent lighting.
-- Josh BoudreauThis isn''t an office. It''s Hell with fluorescent lighting.
hehe, I didn''t get one word of that code you posted, so that''s what C++ looks like =D I guess I need to learn that before going to D3D...
[sorry, totally useless reply] The way I do it, is with functions, the old C style. I have an array of structs for all my sprites, and the function that translates and processes them, loops through the array, and just skips if my bool alive variable is FALSE. Dunno if that helps.
It''''s nice to be important, but it''''s more important to be nice.
Don't we all still remember and miss the day we plotted our first pixel?
