Managing user inputs

Managing the events received from the user is a really important topic. SFML provides us with two different approaches. The first is by polling the events received from a sf::Window instance, and the other is by checking the state in real time of an entry.

First of all, what is an event?

Generally, an event is an object that is triggered when something changes/happens. They are OS-dependent, but SFML provides us with a nice object to handle them in an OS-independent way. This is the sf::Event class. This class deals with a vast number of events, as follows:

Windows contains four different kinds of events. They are as follows:
- Close
- Resize
- Gain/lose focus
- The mouse pointer goes in/out of the window
There are three events for the mouse. They are as follows:
- Move
- Key press/release
- Wheel press, release, or move
The keyboard contains two events. They are as follows:
- Keys press/release
- Text entered
The joystick is also managed with four events. They are as follows:
- Connected/disconnected...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

SFML Blueprints

By : Barbier

SFML Blueprints

By: Barbier

Overview of this book

Managing user inputs

SFML Blueprints

By : Barbier

SFML Blueprints

By: Barbier

Overview of this book

Managing user inputs

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access