SFML community forums

Help => General => Topic started by: rogeriodec on May 30, 2018, 12:40:38 am

Title: [SOLVED] Access Violation in RenderWindow as global, with Visual Studio 2017
Post by: rogeriodec on May 30, 2018, 12:40:38 am

I'm working on a project with Code:Blocks and I decided to migrate to Visual Studio 2017.
Everythig was ok with this project on CB, but now on VS I get a runtime error "Access Violation" on some SFML Classes. They are outside "main".

For example, in any project, just put "Renderwindow" line outside main and you will get the "Access Violation" runtime error:

sf::RenderWindow window(sf::VideoMode(200, 200), "SFML works!");
int main()

Error:

Code: [Select]

Unhandled exception at 0x00007FF8DF70B709 (ntdll.dll) in teste.exe: 0xC0000005: Access violation writing location 0x0000000000000008. occurred
But I need these classes as Global, and as I said, it was ok on CB, so, how can I solve this?

Title: Re: Access Violation in RenderWindow as global, with Visual Studio 2017
Post by: eXpl0it3r on May 30, 2018, 08:02:32 am

Don't use SFML resources including the SFML window as globals. SFML doesn't support this and it's bad design anyways.

Title: Re: Access Violation in RenderWindow as global, with Visual Studio 2017
Post by: rogeriodec on May 30, 2018, 04:31:20 pm

Since I am still a beginner in C++, I am gradually discovering the most common practices in this language, and after reading several opinions, I have realized that global variables are contraindicated in more than 90% of cases because it is dangerous and difficult to control.
I am refactoring my code and I have managed to resolve this error.
Thank you again.