As in title. There's huge issue of text of PyGame_GUI elements not respecting settings scale, which means that themes used through PyGame_GUI .json files have preset sizes that feel too small in big window sizes, but too big in small window sizes - yet they need to somehow be only one value.
This pushes developer (me! haha) to search for middle-ground, but it almost never feels right, and limits a lot. Not to say, now with three managers/theme files, it is a lot of chaos.
What I would suggest is taking advantage of PyGame_GUI flexibility - it can update game's contents on the fly. So, what I'd see as good solution is introducing custom theme.toml file that would handle all categories at once, and it would be modder way to generate PyGame_GUI's .json files.
So you write all of this info in .toml file, the file is read by the game and settings adjust values where needed, then .json files are generated by that data.
When you resize the game, the .json file values are recalculated and regenerated.
As in title. There's huge issue of text of PyGame_GUI elements not respecting settings scale, which means that themes used through PyGame_GUI .json files have preset sizes that feel too small in big window sizes, but too big in small window sizes - yet they need to somehow be only one value.
This pushes developer (me! haha) to search for middle-ground, but it almost never feels right, and limits a lot. Not to say, now with three managers/theme files, it is a lot of chaos.
What I would suggest is taking advantage of PyGame_GUI flexibility - it can update game's contents on the fly. So, what I'd see as good solution is introducing custom
theme.tomlfile that would handle all categories at once, and it would be modder way to generate PyGame_GUI's .json files.So you write all of this info in .toml file, the file is read by the game and settings adjust values where needed, then .json files are generated by that data.
When you resize the game, the .json file values are recalculated and regenerated.