In this file you have a vector of pointers called renderables.
However, it could be called Renderables renderables by a typedef and using unique_ptr.
//std::vector<Renderable2D*> m_Renderables;
typedef std::vector<std::unique_ptr<Renderable2D>> Renderables;
Renderables m_Renderables;
//or even better!
typedef std::map<std::string, std::unique_ptr<Renderable2D>> RenderableMap;
RenderableMap m_RenderableMap;
//now one can access these by name and remove them by name!
This will make it easier to read, and show a good way to handle memory through the use of smart pointers. As standard pointers are dangerous, it is probably better to change the objects that can be changed to unique_ptr as well.
More of an enhancement than an issue...
Sparky/Sparky-core/src/graphics/layers/layer.h
In this file you have a vector of pointers called renderables.
However, it could be called Renderables renderables by a typedef and using unique_ptr.
This will make it easier to read, and show a good way to handle memory through the use of smart pointers. As standard pointers are dangerous, it is probably better to change the objects that can be changed to unique_ptr as well.