CAPE

Oh shit, there my education went out the window. You think you are learnig something, then just: "MINDBLOWN. You dont know anyting. Study harder, douchbag.", or something like that.

 

Well, seems like it will be back to the drawing board. But, as it is an editor, i guess I can have it not som optimized, i guess... (shiver through my body).

 

But dudes, thanks for the quick reply. Very helpful.

I don't know how you store your texture pointers, but with an string identifier, i guessing map<string, TexturPtr>. This will need to be extended to support additional data to use as the identifier.

Here u can implement a functor to create your own comparison function. Its easy to create, you can variate between different types, and is manageble. The problem that occurs is that that you will need to implement a key-struct for each type and combination. But as you currently need to create a load function for each resource type, this I guess will be a minor problem.

struct TextureKey
{
   string name;   //texture name
   int sizeX, sizeY; //texture size
   bool operator<(const TextureKey &a, const TextureKey &b)
   {
	  return std::strcmp(a.name, b.name) < 0 &amp;&amp; a.sizeX == b.sizeX &amp;&amp; a.sizeY == b.sizeY;
   }
};

...

map<TextureKey, TexturePtr> mTexturePtrs;

(Have not tried the above code, but it looks right )