Messages

1

Feature requests / Radian helper functions

« on: April 12, 2008, 02:09:04 am »

In 0x will you be able to define a suffix for literals to convert them? ie my_function(180degrees) or my_function(3.14radians). That would be great if you could, but maybe I'm just completely misunderstanding the proposals.  :lol

2

General / Link errors on linux

« on: April 07, 2008, 04:44:50 pm »

I'm using Ubuntu 7.10 and i've got nvidia-glx-legacy drivers.

Maybe it's just the legacy drivers for rubbish graphics cards?

3

General / Link errors on linux

« on: April 07, 2008, 01:37:38 pm »

It works fine. Linux users with nVidia drivers may need to do what I did which was add "#define glXGetProcAddress glXGetProcAddressARB" to the file Window/Linux/WindowImplX11.hpp before the line "#include <GL/glx.h>"

Or maybe this fix could be added to a configure file or something?

4

General / Link errors on linux

« on: April 07, 2008, 01:03:17 pm »

Ok...

Apparantly because I have nvidia drivers installed there's no such thing as glXGetProcAddress and I need to use glXGetProcAddressARB instead. A page I found on google said I need to "#define glXGetProcAddress glXGetProcAddressARB" before including <GL/glx.h>. (The page was talking about Irrlicht, not sfml, but i assume this might work anyway.)

I've added it to the file Window/Linux/WindowImplX11.hpp. Is GL/glx.h included anywhere else?

It's busy making at the moment. I'll let yous know the results.

5

Feature requests / Sig Slot event handling?

« on: April 06, 2008, 03:23:44 pm »

I might just do that then.

I can understand not wanting to wait for the next standard. Or build your own. But can I ask why not depend on boost? It's a great library and almost definately will become standard eventually. And the two systems could easily coexist.

Still, from what i've seen so far this is a pretty good library anyway.

6

Feature requests / Sig Slot event handling?

« on: April 06, 2008, 02:37:11 pm »

I've just had a wee look at your library and I really like the look of it. I was trying, and failing miserably, to make my own library when my brother suggested I check sfml out and it's great.

The one thing which i think my library did well though was the input handling. Instead of the traditional "while (GetEvents(&event)) {switch (event.type)...}" type thing, you just registered a slot in your initialisation code, and then call "HandleEvents()" and all the signals are emitted.

Is there any chance of anything like this in sfml. IMO it is a much more elegant way of handling events. Boost.Signals is a very nice sig slot library

7

General / Link errors on linux

« on: April 06, 2008, 02:21:42 pm »

First of all this looks like a really great library and I'm glad i found out about it.

I just put the code from the render window tutorial page into a new project on codeblocks, gave it the link options
-lsfml-graphics
-lsfml-window
-lsfml-system

and hit build. And the following error happened:
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libsfml-window.so || undefined reference to `glXGetProcAddress'

Any idea how to fix this?

Edit: If i try running any of the precompiled samples the output is "symbol lookup error: /usr/lib/libsfml-window.so.1: undefined symbol: glXGetProcAddress".