Why does 'mouseButton.button' returns mouse's x position?

[yj1214]

What's the difference between using 'sf::Mouse::isButtonPresessed' and 'sf::Event::mouseButton.button'?

mouseButton function somehow returns the value of the x coordinate of the mouse. Of course it also returns weather I clicked my mouse or not. But why does it return the x coordinate of my mouse?

Finally, which of the above function is recommended?

[Laurent]

What's the difference between using 'sf::Mouse::isButtonPresessed' and 'sf::Event::mouseButton'?

sf::Mouse gives you the current state of the mouse at any time.
sf::Event::MouseButtonPressed notifies you when a button is clicked.
The first is a state, the second is an event. If you don't understand the difference, you can read the corresponding doc and tutorials, this is explained with more details.

But why does it return the x coordinate of my mouse?

Because when you click, you're usually interested to know where you clicked.

[Hapax]

SFML has its own tutorial on these:

• Events
• States (in this context)

Finally, which of the above function is recommend?

Both have their advantages and disadvantages that depend on what you actually want to use them for.
Events are most useful for single instances of controls e.g. mouse clicks, mousewheel scrolled etc. whereas real-time control states are more useful for game controls, for example.

[yj1214]

Thanks for the answers...but I still don't get this one thing.

mouseButton.button function constantly returns the value of my mouse's x coordinate whenever I move my mouse. But why only X coordinate? why not return Y coordinate as well?


Also, how does mouseButton.x and mouseButton.y work?

Code: [Select]

std::cout << mouseButton.x << std::endl;

This prints out Y coordinate of my mouse constantly...when I click my mouse, then it returns my X coordinate...if I need to check where I clicked my mouse, shouldn't the Y coordinate disturbs my X coordinate? how do you distinguish which is my X coordinate?

[Laurent]

You obviously uses events incorrectly. Have you read the documentation first?

[Arcade]

Make sure you understand this paragraph of the tutorial. You may also need to look into the concept of unions if you are unfamiliar with them.

Before dealing with events, it is important to understand what the sf::Event type is, and how to correctly use it. sf::Event is a union, which means that only one of its members is valid at a time (remember your C++ lesson: all the members of a union share the same memory space). The valid member is the one that matches the event type, for example event.key for a KeyPressed event. Trying to read any other member will result in an undefined behavior (most likely: random or invalid values). It it important to never try to use an event member that doesn't match its type.