Alright, So I thought to myself Boy wouldn't it be great if all of the objects stored a pointer to the sprite that I'd like to have them render with? Sounds fantastic to me!

Thus I made this little file looking something like this

//Spritelist.h
#pragma once
#include "Sprite.h"
namespace SpriteList
{
	static Sprite Player1("Rainbow.bmp",64,64,4,4);
}

And then Within the Object class I have there is a Sprite pointer pointing to said static variable. Wow great!

But then onto my Render Method Something appears to be askew!?

//Within some direct3d file
void Direct3D::render_frame(vector<Object> *Objects)
{
	d3ddev->Clear(0,NULL,D3DCLEAR_TARGET,D3DCOLOR_XRGB(0,40,0100),1.0f,0);
	d3ddev->BeginScene();
	d3dspt->Begin(NULL);
	for(vector<Object>::iterator index = Objects->begin();index != Objects->end();index++)
	{
		//does not pass, however if the line fallowing labeled "WiggityWack"it passes then the second time this //function goes by (I assume) it does pass
		if(index->sprite==&Player1)
		{
			index->sprite->frameStore++;
		}
                //"WiggityWack" index->sprite = &Player1;      <- also if the equivilent of this line is //place in the code that calls this render function the top if statement still willl not pass.
		//does pass
		if(index->sprite->cols==Player1.cols)
		{
			index->sprite->frameStore++;
		}
		//index->sprite=&Player1;
                
                //does not render anything
                DrawSprite(index->sprite,1, 64, 64 , 1.0f);
                //Does render something! Wow thats great!
		DrawSprite(&Player1,1, 64, 64 , 1.0f);
	}
	d3dspt->End();
	d3ddev->EndScene();
	d3ddev->Present(NULL,NULL,NULL,NULL);
}

I've done a lot of random tests and I've cut down the problem to the objects within the vector's sprite member simply isn't pointing to that static Sprite called Player1. Static variables have been something I've tried to avoid as I've heard people like to avoid them, so now that I am using one I'm wandering if perhaps I've misinterpretted their use and that's related to why this does not work. Would anyone be able to clarify on this?

I'll post my Object class just in case you see anything stupid there that i totally passed, but i believe there is nothing wrong here.

//Object.h
struct Object
{
public:
	//constructor and deconstructodon Awww yeah!
	Object(/*HWND *hwnd,*/Sprite *_sprite ,int _x, int _y);
	~Object();
	
	// I forget what these are called, uuuuh like... variables inside a class, it's somethin stupid.
	//HWND hwnd;
	Sprite * sprite;
	unsigned int frame;
	int x, y;
	
	//methods
	void update(/*inputdata*/);
};

//Object.cpp
Object::Object(Sprite *_sprite ,int _x, int _y) :sprite(_sprite), x(_x), y(_y),frame(0)
{
}
Object::~Object()
{
}
void Object::update(/*inputdata*/)
{
}

I am aware that keeping this in global space is to be avoided, I'm just not sure how one would go about doing this without doing so. I would like to be able to have something like this for the constructor of the child class of an object

//PlayerSpt Sprite("File",blabla variables n crap)
//Player class, child of Object class
Player(x,y):Object(&Player,x,y)

But it needs to be accesible to my method that loads in all of the graphics. Does anyone have some advice on how I might do this, is there some other method people would advise for doing this or am I just dreaming and will have to use one of the other idea's I've come up with such as using an intager instead of a sprite pointer and making the sprite only accesible to the d3ddevise and using the intager to pick which sprite is being used.

You could do this plenty of ways but your idea about using an integer instead of a pointer is sensible. I'd suggest looking into that more. Using an integer or a handle or really any mechanism for keeping a 'name' to your referenced object would be better than keeping a pointer directly all the time. And as you've already guessed you can start limiting how much of your code needs to know specifics like what a Sprite is.

Beautiful! I had an idea of something similar to that but there where a few things that just... I dunno I felt like they would be messy. What you've written up there looks very clean and usable. There are a few keywords I've never seen before, but I'm sure I'll be able to look those up for the most part. I'll let you know if I'm having any troubles in that regard.