Hello.
I spent some time writing resource manager, but then I noticed that tgui::Picture, unlike sf::Sprite, doesn't need it Texture to be alive after setTexture has been called. Is it true? If so, I can get rid of all the ptrs I used because it will work just fine like this:
1. Create/Load sf::texture.
2. Bind texture to tgui::Picture.
3. Don't care about sf::Texture anymore, tgui::Picture has stored the object itself and not a pointer.
How is it implemented? Is there any unneeded work transfering the texture? Or it just pointer transformed into something like shared_ptr so it will be saved without any additional memory management?
Also, what's the purpose for tgui::Texture class? I saw some widgets require it, but they also fine with sf::Texture.