Add autosave for configuration and SRAM. (Bugzilla #27)

[GerbilSoft]

status IN_PROGRESS severity enhancement in component gens for II 1.0_beta1
Reported in version r7 on platform All
Assigned to: David Korth

On 2009-12-08 16:36:35 -0500, David Korth wrote:

Gens/GS currently only saves configuration on exit (or manual "Save Config As..."), and currently only saves SRAM when a ROM is closed.

Configuration should be saved whenever the configuration is updated. (Well, either that or on a five-second update cycle.) The INI handler should be improved performance-wise before this is done, since it's currently rather slow. Consider using SimpleIni: http://code.jellycan.com/simpleini/

SRAM should be checked for modifications every 5 seconds or so, and if there's any modifications, it should be saved. (Add a 'dirty' flag instead of checking the SRAM data, as well as a "highest address accessed" variable.)

On 2010-09-17 04:25:20 -0400, David Korth wrote:

SRAM and EEPROM autosave is implemented in Gens/GS II.

Configuration autosave is not implemented, since configuration isn't saved (or even configurable) at the moment. Retargetting for II 1.0_pre1.

On 2010-09-17 04:26:08 -0400, David Korth wrote:

(In reply to comment # 1)

SRAM and EEPROM autosave is implemented in Gens/GS II.

Configuration autosave is not implemented, since configuration isn't saved (or
even configurable) at the moment. Retargetting for II 1.0_pre1.

Additionally, SRAM/EEPROM autosave needs to be invoked if a savestate containing SRAM or EEPROM is loaded.

On 2011-02-18 13:52:41 -0500, David Korth wrote:

(In reply to comment # 2)

Additionally, SRAM/EEPROM autosave needs to be invoked if a savestate
containing SRAM or EEPROM is loaded.

SRAM autosave is invoked when a savestate is loaded since commit SHA: 9b1d5a7.

TODO: Add EEPROM support to ZOMG savestates, and implement autosave for that.

TODO: Autosave GensConfig after a certain amount of time since the last modification.