What I mean is that you will only have one instance and only one pointer to this image and this will make your code faster and use less memory since you don't need 50 pointers to the same image! Just use one pointer for the image you need. I did notice I didn't show you how to use the static data from the class so here it goes:

// [Global scope:]
class Data
{
static int iX, iY;
};
int Data::iX = 0;
int Data::iY = 0;

// [Function scope:]
void SomeFunction()
{
Data *pData = new Data;
pData->iX = 50;
}
pData->iY = 40;

Hope that helps!:)

You cannot delete a bitmap

I prefer the idea of a singleton holding all the images, and the mobiles requesting pointer to a const BITMAP for them to blit.

To 23yrold3yrold:
Quote:
Okay, I create 50 enemies, call LoadImage() so they all have the image, one enemy dies ... and I'm screwed. I also like the idea of seperate pointers for enemies so I could, say, create 4 slightly different images/animations for an enemy for variety's sake, so it doesn't just look like the same boring enemy clones running around. Or you could use the same enemy class with different level-specific graphics (tons of platformers and shooters do this).

If you read his openning question on this thread...
Quote:
...the problem is that ALL darkstar have the same image...

I KNOW that if you did what you say you would not be able to use differant images, but he said that he only has one!;)

Also, checking to see if the pointer is NULL or not will save a run time error if you delete a pointer twice...it is also good coding practice!:P

I DID do a no no though:(, I didn't write destroy_bitmap(pImage);)
My bad...I didn't mean to type delete pImage...8-)

I retract my statements...I messed up:D

You could use ref counts such as:

class Object
{
public:
Object()
{
pImage = NULL;
iRefCount++;
}
~Object()
{
iRefCount--;
if (iRefCount==0)
destroy_bitmap(pImage);
}
static BITMAP *pImage;
unsigned long iRefCount;
};

And yes, having just the pointer around harms no one, but when he's got 50 or so pointing to and having loaded all of the same image it is a huge waste and unneccassary when all you need is one BITMAP loaded!:o

I'm talking about when he has all 50 loaded using load_bitmap::)...not the 50 pointers...even though if you could use one instead of 50...well that's still another improvement...I KNOW NOT MUCH:P