Messages

1

General discussions / Re: SFML 2.0 RC

« on: June 25, 2012, 12:22:57 am »

Sorry, I don't see how this could be added without breaking API compatibility?

Adding a member to a struct, and an argument with default value to a function doesn't break API compatibility.

So when you say that the 2.0 API should not be broken, you exclude the C API?

2

General discussions / Re: SFML 2.0 RC

« on: June 23, 2012, 11:28:24 pm »

So this is impossible with SFML ?

Indeed. This feature is not implemented yet.

I have read that there will be no change in the API 2.0 until 3.0.

The API can't be broken, it must remain backward compatible. But it doesn't mean that new things cannot be added.

Sorry, I don't see how this could be added without breaking API compatibility?

Wouldn't it be better to add the mouseID field to the event struct, and the mouseID parameter to the sf::Mouse methods now (even if it's ignored at the beginning), so that it wouldn't break 2.0 API when we add this feature?

3

General discussions / Re: SFML 2.0 RC

« on: June 23, 2012, 09:41:01 pm »

Hi,
it seems there is an issue with the API 2.0.

I post it here, not in feature request because I have read that there will be no change in the API 2.0 until 3.0.

It seems that it is possible to plug several joypads into the same computer to play multiusers game because there is a joypadID field in the event structure, but it seems that there is no equivalent for mices!

With the SDL it is possible to handle one mouse for each player. So this is impossible with SFML ?