Way to NOT pass reference to RenderWindow to a class?

[pteberf]

Greetings, people!

I am developing a video game using SFML and nearly every drawable entity has its own class. There is also a somewhat engine class, containing my RenderWindow.

The problem is that in order to call window's draw() method in any drawable entity's entity_draw() method, I have to either pass a window reference to the entity_draw() method, or have a reference as a member of entity's class and initialise it in a constructor, obvioulsy passing RenderWindow reference to the constructor.

Both variants are very annoying and I am wondering whether there is a good way to "globalize" the RenderWindow somehow.

The best solution I found was creating another class, containing only the window and a videomode(MainWindow class) so they could be accessible from any project file. These two were private static members and constructor and destructor were also private, so I got somewhat of a static class. This however produced an unresolved external symbol error and trying to initialise RenderWindow and VideoMode in different ways didn't produce any result.

Help? 
Thank you.

[korczurekk]

Your class should inherit sf::Drawable and overload "draw" function, then you will be able to do something like that:

MyClass myObj1;
//...
window.draw(myObj1);
 

EDIT: http://www.sfml-dev.org/documentation/2.0/classsf_1_1Drawable.php

[Laurent]

If you want to draw to something then you have to pass this something to the function that does the drawing, I find this very natural and not annoying at all. And this is how everyone else does it too.

If you really want to use static members, then at least learn how to define them correctly (hint: Google know how to do this very well ).

[pteberf]

If you want to draw to something then you have to pass this something to the function that does the drawing, I find this very natural and not annoying at all. And this is how everyone else does it too.

@Laurent thanks for feedback. I'll stick with passing the window then. I just thought that not doing it might have been better and I am apparently wrong. 

[BlueCobold]

You might consider only passing a RenderTarget& instead of a RenderWindow&.