New global inputs in SFML 2

[Nexus]

people will hate me if I change the same code everyday

Don't they hate you even more if you change it every week, so that they have already adapted all their code and can change it again?

But I think apart from bindings like Groogy's, this change isn't problematic. As we concluded earlier, the method to get the desktop position is nearly useless anyway

[Hiura]

But I think apart from bindings like Groogy's

and the Mac port. :roll:

[Nexus]

In C++, you can directly implement overloaded functions, while Groogy has to find ugly workarounds. For the Mac port, you only need to rename the function.

[Hiura]

For the Mac port, you only need to rename the function.

I was referring to that. If it's only a rename thing then it's fine, goes fast and everybody is happy. But if the API changes everyday (like sf::Input to what's now) I'll get crazy (OS X is a mess for low-level application, really! When I'll commit the update for the new input system you'll understand my pain.).

Laurent, I'm of course not saying that you should not change anything. Hell no! But don't do it every day, please.  :lol:

[Nexus]

Well, I'm not unhappy either if the SFML API doesn't change every day, since I have much dependent code, especially in Thor. But sometimes, API breaks are worth the new features

[Laurent]

Don't forget that:
- SFML 2 is not even in alpha state so I can change whatever I want, whenever I want :lol:
- once SFML 2 is officially released, I won't break the API anymore in the 2.x branch

[Nexus]

Now that SFML has sf::Vector2u for unsigned int, why don't sf::Mouse::GetPosition() and sf::Mouse::SetPosition() use it?

For example, it would simplify the usage with sf::RenderWindow::ConvertCoords(), even more if there were a direct overload to take vectors instead of separate unsigned ints.

[Laurent]

Now that SFML has sf::Vector2u for unsigned int, why don't sf::Mouse::GetPosition() and sf::Mouse::SetPosition() use it?

I didn't see any reason to disallow coordinates outside the screen.

For example, it would simplify the usage with sf::Window::ConvertCoords(), even more if there were a direct overload to take vectors instead of separate unsigned ints.

Hmm that's true.

[Hiura]

I've implemented the keyboard and mouse part of the new input system. Could some of you check if it works fine on your computer too ? Thanks.
(Joystick part will follow soon.)

[Contadotempo]

I'm a bit embarrassed to ask because it's probably really simple but,
What replaced the real-time input function GetInput()?

[Laurent]

Nothing. The new system is only made of static class functions, so they can be called directly without instanciating or getting anything.

[Contadotempo]

Ah I understand now. Thank you.

[pdinklag]

Nice!
Looks like I need to get the latest build and update JSFML.

[Haikarainen]

Nice stuff! Think i'll wait until SFML2 is fully released before i updated my libraries again though, have toooo much to fix right now

[coolhome]

Very nice! I love the new API for inputs. I went to update to the latest commit (since I was behind a few) and it totally broke my engine. I was wondering where some of the functions went haha I guess that's the price of development releases. Keep it up.