Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
What compiler are you using? Visual studio?
Make sure you are building an application and not a library. Then, make sure you read the building log. I'm sure there are errors there.
SFML outputs to std::cerr, and any standard stream can be redirected to whatever you want: a file, nothing, etc.
You can try this:Code: [Select]std::cerr.rdbuf(NULL);
If you are using Visual Studio just set the Subsystem to Windows. The Console will disappear.
Quote from: "coolhome"Do I always need to add the * when setting the image? just wondering if there is a way to remove it...
Just return a reference instead of a pointer.Code: [Select]sf::Image& ImageManager::Get(const std::string &Key);
#pragma once
#include "Includes.hpp"
class ImageManager {
public:
typedef pair<string, sf::Image*> Images;
typedef map<string, sf::Image*> ImagesMap;
ImagesMap manager;
ImageManager();
~ImageManager();
bool Load(const string &Key, const string &Filename);
sf::Image* Get(const string &Key);
};#include "Includes.hpp"
ImageManager::ImageManager() {
}
ImageManager::~ImageManager() {
while(manager.begin() != manager.end()) {
delete manager.begin()->second;
manager.erase(manager.begin());
}
}
bool ImageManager::Load(const string &Key, const string &Filename) {
sf::Image* image = new sf::Image();
if(! image->LoadFromFile(Filename) ) {
delete image;
image = NULL;
return false;
} else {
manager.insert(Images(Key, image));
return true;
}
}
sf::Image* ImageManager::Get(const string &Key) {
sf::Image *resource = NULL;
ImagesMap::iterator it = manager.find(Key);
if(it != manager.end()) {
resource = it->second;
}
return resource;
}ImageManager manager;
sf::Sprite mouse;
if(! manager.Load("mouse", "mouseGraphic.gif")) {
//error here
}
mouse.SetImage(*manager.Get("mouse"));struct spriteStruct {
sf::Image Image;
sf::Sprite Sprite;
int x;
int y;
float rotation;
sf::IntRect SubRect;
};
typedef std::pair<std::string, spriteStruct> value_type;
std::map<std::string, spriteStruct> sprites;
std::map<std::string, spriteStruct>::iterator spritesIterator;
void loadimage(std::string key, std::string Filename) {
spriteStruct _spriteStruct;
sprites.insert(std::pair<std::string,spriteStruct>(key,_spriteStruct));
sprites[key].Image.LoadFromFile(Filename);
sprites[key].Sprite.SetImage(sprites[key].Image);
}struct sprite {
sf::Image Image;
sf::Sprite Sprite;
int x;
int y;
float rotation;
sf::IntRect SubRect;
};
typedef std::pair<std::string, sprite> value_type;
std::map<std::string, sprite> sprites;
std::map<std::string, sprite>::iterator spritesIterator;
void loadimage(std::string key, std::string Filename) {
sprite _spriteStruct;
sf::Image _load;
sf::Sprite _sprite;
if(! _load.LoadFromFile(Filename)) {
//error
}
_spriteStruct.Image = _load;
_spriteStruct.Sprite = _sprite;
_spriteStruct.Sprite.SetImage(_spriteStruct.Image);
sprites.insert(std::pair<std::string,sprite>(key,_spriteStruct));
}You have to be particularly careful when manipulating images. A sf::Image instance is a resource which is slow to load, heavy to copy and uses a lot of memory.
A lot of people, especially beginners, will just put an instance of sf::Image wherever they have an instance of sf::Sprite, because it may seem the simplest way to draw something. The fact is that it's generally a bad idea. The most obvious problem is when copying such objects (just putting them into an array generates copies) : the sprites will most likely appear white. The reason is that a sprite only points to an external image it doesn't own one, so when the image is copied the sprite has to be updated to point to the new copy of the image. This is quite easy to handle, you just have to define a copy constructor for such classes holding (or deriving from) a sprite and an image