-
-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface setting in "Evil" or "Good" mode is not retained when the user goes to the Home screen and returns to the game #2450
Comments
Hi, @LeHerosInconnu |
Not sure about that. But in any case, if the user makes changes anywhere in the interface, they must be taken into account. Also I think that the option "game: use evil interface" should be removed from the options in the "Experimental Game Settings" window. |
@LeHerosInconnu. |
Changes made by the player should always be saved, even the next time the program is started. |
It's heavily broken. 👎 In fheroes2: 2020-12-20.15-43-19.mp4 |
@LeHerosInconnu. |
I've checked the OG. It works simply there: once you've changed GUI "Evilness", it will be evil everywhere. Each time you load, or start new game. That's true. |
In fheroes2, the "Interface Dynamic" setting of the original game is missing: #1329. :) |
@LeHerosInconnu |
If you start a scenario with the dynamic interface, the game will select the interface accordingly. |
Did the PR #5272 solve this? It seems like this and #5251 were duplicate issues, although some other points are raised in later comments here, like interface type being saved for every save file. Maybe the issue title should be changed or the issue should be closed @LeHerosInconnu? |
Hello @zenseii, The problem described in the original post seems to be solved. |
In fheroes2, the interface setting in "Evil" mode or "Good" mode is not retained when the user goes to the Home screen and returns to the game.
In the example, when the user returns from the Home screen, the interface should be "Good".
In fheroes2:
2020-12-20.11-13-28.mp4
The text was updated successfully, but these errors were encountered: