2dc4352845
The above issue was caused by the fact that image::flush_cache() wasn't called after reload_changed_game_config() when the addons manager was exited. Using F5 at the tilescreen caused the image to appear since that callback *did* include image::flush_cache(); reload_changed_game_config() was called in 5 places, 2 of which were followed by flush_cache. I figured it's safest to just include the latter in the former, since the other three usecases (multiplayer installed addons before joining a game, a new core was selected, and the addons manager was exited) all seem like places where flushing the image cache would be appropriate.
About
The Battle for Wesnoth is an Open Source, turn-based tactical strategy game with a high fantasy theme, featuring both singleplayer and online/hotseat multiplayer combat. Fight a desperate battle to reclaim the throne of Wesnoth, or take hand in any number of other adventures.
License
Please see the wiki for information regarding The Battle for Wesnoth's licensing:
https://wiki.wesnoth.org/Wesnoth:Copyrights
Installing
See INSTALL for instructions on how to build the game from source code.
More Information
For extensive documentation about all aspects of the game, see the official Battle for Wesnoth web site.
A (translated) description of how to play the game can be found in doc/manual/manual.*.html, or online at:
https://wiki.wesnoth.org/WesnothManual
The official Battle for Wesnoth Forums (with over 400,000 posts from more than 20,000 registered members) can be found at: