News:

Printed Amstrad Addict magazine announced, check it out here!

Main Menu
avatar_roudoudou

Snapshot loading behaviour in an emulator

Started by roudoudou, 07:46, 07 September 23

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Snap loading behaviour

 A snapshot must reconfigure the emulator to match the snap as closely as possible
4 (28.6%)
A snapshot must not change the configuration (e.g. to test code on other confs)
0 (0%)
The emulator must always ask in the event of a conflict
7 (50%)
D, the D response
1 (7.1%)
An option must tell you what to do once and for all
1 (7.1%)
Something else
1 (7.1%)

Total Members Voted: 14

roudoudou

My pronouns are RASM and ACE

McArti0

C with button option A and button option B and Reset to C in menu.
CPC 6128, Whole 6128 and Only 6128, with .....
NewPAL v3 for use all 128kB RAM by CRTC as VRAM
TYPICAL :) TV Funai 22FL532/10 with VGA-RGB-in.

eto

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)





OffseT

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)

Powered by SMFPacks Menu Editor Mod