SFML 2.0 RC

[mobai]

I already asked in the chat and it looks like there's something between sfml and the drivers that doesnt work well...

The whole thing is explained here: http://en.sfml-dev.org/forums/index.php?topic=9074.0

[Foaly]

I'm not sure, but i think i found an error in the documentation of sf::Shader...
If I create a shader like this:

sf::Shader shader;
shader.loadFromFile("Shader.frag", sf::Shader::Fragment);

and use it like it says in the documentation:

m_RenderTexture.draw(m_Circle, shader);

I get an error. It works when I do this:

m_RenderTexture.draw(m_Circle, &shader);

Same with the example that uses the renderstates. I have to pass the address not the value, like it says in the documentation.

[eXpl0it3r]

m_RenderTexture.draw(m_Circle, &shader);

And that worked?

The draw function is taking the render states as reference, thus passing the adress to the function shouldn't work at all either...

See the two draw function declerations and the header to it.

Edit: I just now figured out how that all worked, since the documentation said that draw(obj, shader) is a short cut, but I couldn't see how it's being done, then I saw that the sf::RenderStates class has a constructor that takes a pointer to a sf::Shader and thus you indeed need to call draw(obj, &shader), which invokes that said constructor, creates a sf::RenderStates class and passes it as reference to the draw call. I don't know why the constructor takes pointers rather than references...
But if you use a RenderStates object yourself you shouldn't need to pass the adress.

[Foaly]

Yeah it works! Look closer Here is why: if you pass a shader the second argument to the draw function it is passed on to the constructor of the RenderStates, which has a constructor that takes a shader as a argument. Really nice shortcut

edit: But still, the constructor of the RenderStates only takes a pointer to a shader. So I think there is an error in the documentation.

[eXpl0it3r]

Yeah it works! Look closer Here is why: if you pass a shader the second argument to the draw function it is passed on to the constructor of the RenderStates, which has a constructor that takes a shader as a argument. Really nice shortcut

Yep, noticed that myself...

edit: But still, the constructor of the RenderStates only takes a pointer to a shader. So I think there is an error in the documentation.

Yep, it's a mistake, but I wonder why use a pointer instead of a reference?

[Foaly]

Yep, noticed that myself...

Yeah it is kinda tricky, but a really cool shortcut!

Yep, it's a mistake, but I wonder why use a pointer instead of a reference?

I haven't thought about that... Maybe there is a reason for it. We'll see what Laurent says

[Laurent]

The reason is simple: null pointer = no shader.

I'm going to fix the doc, thanks

[Foaly]

... makes sense

No Problem. I'm glad I was able help

[Laurent]

In fact it was already fixed, the online doc is just outdated.

[pdinklag]

I got Windows 8 Professional from my university and will install it sometime later this week. So unless anybody has done this already, I will soon let you know if SFML works well on Windows 8.

[Andrei15193]

I got Windows 8 Professional from my university and will install it sometime later this week. So unless anybody has done this already, I will soon let you know if SFML works well on Windows 8.

It works, even on Intel GPU (I have a MSI U123 Wind with 1Gb of RAM and Intel Atom 1.66 Ghz and Intel GPU). If I try to compile and run the same code I have on Ubuntu it crashes (some OpenGL crash), so... go go Win8.

Also, I am using VS2012 Pro using SFML .dll files from VS2010 download, so far they work (RenderTexture, RenderWindow, Sprite, Events it's all I've tried out yet).

Off topic:
Before installing Win8, if you want to use Metro style apps you need a min 1024x768 screen res to run them. My notebook doesn't have that res but installing software the old fashion way and runing them from desktop works just fine.

[Groogy]

It works just fine on Windows 8, even rbSFML does, already tried

Though cmake don't like Visual Studio 11 yet(2012)

[eXpl0it3r]

Though cmake don't like Visual Studio 11 yet(2012)

What do you mean by that?
I've no problems with VS11 and CMake. Do you have the latest CMake version?

[Groogy]

Don't know, might have done something wrong cause it just didn't want to generate the needed files. Gave some error I don't remember but that didn't make sense.

[eXpl0it3r]

Don't know, might have done something wrong cause it just didn't want to generate the needed files. Gave some error I don't remember but that didn't make sense.

Yeye it's always the fault of the software...