Follow-up Comment #2, bug #14460 (project wesnoth):
> I dont think loadgame::show_dialog erasing the gamestate is the source of
the bug
It is. The engine is processing an event, which means that scoped WML
variables are in use. After displaying the loadgame dialog, the game state is
erased and an exception is thrown. As a consequence of the throw, the stack is
unwound, objects created while processing the event are destructed, including
the scoped WML variables. The destructor of these variables then fails, as it
is unable to restore the game state in its pre-event state.
The game state should not be erased until the current scenario has actually
been terminated! In other words, the game state should be erased after the
exception has been thrown, not before.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?14460>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
