SFML 2.0 GetInput()

[pighead10]

What should I use instead? I know sf::input got replaced by sf::Keyboard and sf::Mouse, but I cannot find any function like GetInput() in the documentation under Window. I'm trying to achieve something like this in the 1.6 tutorial:

Code: [Select]

// Get some useless input states, just to illustrate the tutorial
        bool         LeftKeyDown     = Input.IsKeyDown(sf::Key::Left);
        bool         RightButtonDown = Input.IsMouseButtonDown(sf::Mouse::Right);
        bool         JoyButton1Down  = Input.IsJoystickButtonDown(0, 1);
        unsigned int MouseX          = Input.GetMouseX();
        unsigned int MouseY          = Input.GetMouseY();
        int          JoystickX       = Input.GetJoystickAxis(1, sf::Joy::AxisZ);
        int          JoystickY       = Input.GetJoystickAxis(1, sf::Joy::AxisY);
        int          JoystickPOV     = Input.GetJoystickAxis(1, sf::Joy::AxisPOV);

[Groogy]

Check the documentation. They are just global functions.

[Anata]

Code: [Select]

const sf::Input& Input = App.GetInput();

After that, you can use this code

[Laurent]

Code: [Select]

const sf::Input& Input = App.GetInput();

After that, you can use this code

He wants the equivalent in SFML 2

[Nexus]

Check the documentation.

Yes, that's the best source until the tutorials of SFML 2.0 are written.

They are just global functions.

No, they're static functions of the classes sf::Mouse, sf::Keyboard, sf::Joystick.

Code: [Select]

const sf::Input& Input = App.GetInput();

He uses SFML 2, so sf::Input won't help him.

[nitrix]

[...]
Event someEvent;
window.PollEvent(someEvent);
[...]
switch (someEvent.type) {
case sf::Event::KeyPressed:
//event.key.code....
//sf::Keyboard::Escape...
}

The event structure will get filled with all the data needed about the event. event.type tells you what kind of event it is (mouse, keyboard, etc). Process everything in a switch case (: Then you can set your own booleans and stuff.

[Laurent]

He wants the equivalent of sf::Input, not events (which haven't changed much).

[nitrix]

I didn't know there was a difference. Both are very similar and events are even easier to work with.

[phufhi]

You can find the equivalent code for sf::input in the sfml 2 documentation.

However, I would like to know why GetMouseX() and GetMouseY() have been replaced with GetPosition(), which returns a "Vector2i". It seems to me that this is less convenient.

[Laurent]

However, I would like to know why GetMouseX() and GetMouseY() have been replaced with GetPosition(), which returns a "Vector2i". It seems to me that this is less convenient.

See by yourself:

Code: [Select]

// current API

int x = sf::Mouse::GetPosition().x;
int y = sf::Mouse::GetPosition().y;
sf::Vector2i pos = sf::Mouse::GetPosition();

Code: [Select]

// what you want

int x = sf::Mouse::GetPositionX();
int y = sf::Mouse::GetPositionY();
sf::Vector2i pos(sf::Mouse::GetPositionX(), sf::Mouse::GetPositionY());
What I want to highlight is that extracting components from a vector is just one extra character to write, whereas constructing a vector from separate components can be really verbose.
And although it doesn't have a significant impact, the second solution would require to call the same underlying OS-specific function twice.

[phufhi]

Thanks, Laurent!
I am new to sfml and relatively new to programming.
I did not know you could get the coordinates this way!