[SOLVED] Save/Load keybindings

[Glocke]

Hi,

I'm using ini-files to save and load keybindings. Using sf::Joystick is quite easy: I read/write the buttons' uint's. Handling axis is nearly the same, but I'm using a small function mapping "x" to sf::Joystick::Axis::X and so on. But doing this for keyboard (e.g. "w" to sf::Keyboard::W) isn't fun at all. Is there a clever way to do this? I want to avoid a large switch considering the entire sf::Keyboard enum. Maybe there's a way?

[eXpl0it3r]

You could take a look at Thor's action system.

[Nexus]

More precisely, the Thor header InputNames.hpp will help you

[Glocke]

Well, (for me) it seems like Thor creates a hashmap to map sf::Keyboard::Key to std::string and vice versa..

What's about the enum values of sf::Keyboard::Key. Afaik every C-style enum is based on int-values (but aliased by the enum). So the sf::Keyboard::Key's should use int values at the internals. Are these values deterministic? The first two enum elements explicitly carry the values -1 and 0 - this might imply B as 1, C as 2 and so on. Testing this (means: converting to integer and printing to stdout) confirmed this - at least for the first 4-5 elements.
But these values should be deterministic, because of the two initial values, aren't they?

[Nexus]

If deterministic means that every compiler translates the enumerator's values to the same integer: yes

If deterministic means that you can serialize the numbers and future versions will still be compatible: no
That's why you should prefer string serialization. It can also be read and written by humans.

[Glocke]

If deterministic means that you can serialize the numbers and future versions will still be compatible: no
That's why you should prefer string serialization. It can also be read and written by humans.

Ok thanks. I guess I'll adapt Thor's mapping approach in the near future.

[Nexus]

You could also just use it

If you don't want to install and link Thor, you can also copy the files (just keep the license). The advantage is, when SFML supports more keys, I will adapt Thor correspondingly, so your code works automatically with more keys.

[Glocke]

You could also just use it

At the moment I don't want to add extra dependencies to my project. But I thinkg if I'll need more Thor-features later, I'll use it

If you don't want to install and link Thor, you can also copy the files (just keep the license). The advantage is, when SFML supports more keys, I will adapt Thor correspondingly, so your code works automatically with more keys.

 

[Rosme]

You could also just use it

At the moment I don't want to add extra dependencies to my project. But I thinkg if I'll need more Thor-features later, I'll use it

Considering the license and how easy it is to use, the reason of adding extra dependencies shouldn't be. You'll find that Thor offers a lot of thing that can be usefull. This looks to me like a case of NIH.

[Glocke]

Well, that's why I finally added Thor to my project to load keybindings