SFML community forums

Help => Window => Topic started by: djm_jm on January 17, 2017, 05:41:54 pm

Title: Failed to activate the window's context
Post by: djm_jm on January 17, 2017, 05:41:54 pm
I installed SFML on windows and have one error. The screen of window is not drawned, only a white empty window.

I put one attachment (it has a image) to show the error.

My codeblock's version is 16.01 and the SFML's version is GCC 4.9.2 TDM (SJLJ) - 32-bit.

Anybody can help me fix that?
Title: Re: Failed to activate the window's context
Post by: Mr_Blame on January 17, 2017, 05:58:54 pm
Is your the compiler, with which SFML was built the exactly the same compiler as your? Did you install new drivers?
Title: Re: Failed to activate the window's context
Post by: djm_jm on January 17, 2017, 06:29:07 pm
Is your the compiler, with which SFML was built the excavation same compiler as your? Did you install new drivers?

Good, now I downloaded other version of SFML and it appears a new problem. Now the program is no execute and is showing the message bellow on image attached.

EDIT: I can't install the visual c++, happens one error and the installation abort.
Title: Re: Failed to activate the window's context
Post by: Mr_Blame on January 17, 2017, 06:53:55 pm
Try to build SFML yourself from source
Title: Re: Failed to activate the window's context
Post by: djm_jm on January 19, 2017, 07:26:36 pm
Well, I cann't fix the error on windows 7, so I installed the Windows 10 and put the gcc/g++ compatible with SFML version. This time I don't use the codeblocks and I try build SFML myself from source through CMD prompt. Works fine!!!

I have a question:

What IDE you use with SFML?
Title: Re: Failed to activate the window's context
Post by: Mr_Blame on January 20, 2017, 05:55:51 pm
I use visual studio 2015 community, so I won't have to compile SFML myself plus I get not bad user interface and it's free.
Title: Re: Failed to activate the window's context
Post by: eXpl0it3r on January 20, 2017, 06:25:40 pm
The compilation of SFML really has nothing to do with this. You most likely didn't have an up to date GPU driver.