@Jesper Juhl
Going to take a look at it, thanks.
@Ixrec
Oh, okay. If the problem isn't solved (I think I have a hunch of how I might solve it right now), I'll post that version of my code here =)
@eXpl0it3r
Actually, I thought that the pointer WILL persist, since it IS a pointer and you have to manage its lifetime manually: Thats why I choose a pointer for the "Texture", and not only a Texture-Object itself. And I don't really think that the problem lies in that method, since the Texture/Sprite still exists when I request it from my BallEntity class (= Doesn't get destroyed after loading), but it just somehow gets destroyed before I can render it. It's weird, in my opinion. But after all, I'm new to C++... I'll take a look at RAII but I don't really like it since the syntax just looks so.. complicated, for something that should make your life easier. I dunno, it's just a feeling I get.
Besides...
May I ask where do I copy it? I mean, I thought that what I was doing was exactly the contrary, not copying it, since I work with pointers instead of the object itself?
Man, I really hope I'll understand this C++ stuff with pointers sometimes