Settings system to save variables about horsemenu HOT 5 CLOSED

I could just port over the one from YimMenu as it works just great.

from horsemenu.

std::map<string, std::any>

from horsemenu.

The main downside of using that one is that changing one single line requires a full recompile of the menu.

It would be good to take a look at separating settings to their specific features.

from horsemenu.

The main downside of using that one is that changing one single line requires a full recompile of the menu.

It would be good to take a look at separating settings to their specific features.

Wouldn't having saving structs have their own file instead of hosting all in the settings.hpp file already suffice?

from horsemenu.

What about a dynamic container? It would definitely impact performance to some degree maybe noticeable maybe not but it would be very easy to save, load and edit.

from horsemenu.