Associate config data with an image

[GoogleCodeExporter]

Currently you can save a lot of metadata for a disk image like screenshots, 
publisher, etc. It would be great if you had the option of saving the current 
config just to a particular image for games where you want to have particular 
key bindings or whatever.

Original issue reported on code.google.com by nebnos...@gmail.com on 6 Jun 2012 at 9:49

[GoogleCodeExporter]

When you save the game state also the current key binding is saved.

"When you save the game state also some preferences are saved in the state 
(joystick buttons, screen format, joystick port, 1541 emulation, rumble)"

Original comment by olimpier...@gmail.com on 25 Dec 2012 at 7:08

• Changed state: Invalid

[GoogleCodeExporter]

Sorry maybe I wasn't very clear. Want I meant was being able to save DIFFERENT 
configurations for DIFFERENT images.

This would make it easy to save custom key bindings and drive emulation options 
etc. particular to each game.

Original comment by nebnos...@gmail.com on 27 Dec 2012 at 9:27

[GoogleCodeExporter]

When you save the state of a game these particular settings are saved:

Display Type,  Joystick Swap,  drive Emulation, key bindings.

If you look at the "save" directory there are configuration files for each 
saved game with the name "gamename.sav.prefs".

They are loaded when you load the game state.

So, if you want to have a particular key binding you should load the game, 
configure the key bindings and the other settings and then save the game state.

To load the saved configuration you should then load the game state.

If you mean to have differnt configurations for one game, I do not see the 
useness. 

Original comment by olimpier...@gmail.com on 28 Dec 2012 at 11:56