Question:
Snap loading behaviour
Option 1: A snapshot must reconfigure the emulator to match the snap as closely as possible
votes: 4
Option 2: A snapshot must not change the configuration (e.g. to test code on other confs)
votes: 0
Option 3: The emulator must always ask in the event of a conflict
votes: 7
Option 4: D, the D response
votes: 1
Option 5: An option must tell you what to do once and for all
votes: 1
Option 6: Something else
votes: 1
Just thought about it. For enthusiasts C is clearly the preferred way but for users who just want to enjoy their game, A might be easier.
C': The emulator must ask in case of a conflict but offers the option to save the answer for the future - "never ask me again". (and of course the possibility to revoke that choice in the settings)
ACE is between B and C.
It won't change the current configuration, will load the snapshot "at best", and tell the user about the detected mismatches (different CRTC, missing memory...) so that he could adapt the configuration if expected.
But instead of displaying a simple notice about the mismatch, I could actually add a button to the requesters so that the adaptation could be one click (with as well the appropriate default choice option as suggested by
@eto).
Sounds good, and quite easy to achieve. 8)