store custom input configurations in unique file?

[Marcuz]

my reason is that the 4 custom configurations should be enough for different needs and inputs, so it could be useful for them to be stored in a single file outside the present *.uae.

the pros would be that if you'd start a vanilla quickstart configuration, you would not need to set custom joystick input (particularly if you have many joysticks), screenshots key, quick load quick save etc.

Of course you could copy and paste manually all that information in the host config. files (i did it sometime, but they gets overwritten if you don't remember it when you update winuae).

the cons is that this way, older configurations using them would need the input to be resetted once for each one.


would it be useful?

[Toni Wilen]

I could do this but only if I can remove "old-style" input configuration included with main config file. (I don't want to make it too complex)

What about this:

Configuration store works like in Filters-page. (select box with file names, load/save-buttons)

Configuration #1-#4 will be replaced with list of stored input configurations (can be renamed by user)

Only name of input configuration file will be stored in main config file.

"Old style" configuration files (that include input data) will be supported when reading but input panel data won't be written back to main config file anymore. (that should be enough backwards compatibility..)

Only problem is lack of GUI space..

[Marcuz]

Toni do it just if you think it's useful or there's no cons to it, i mean if i'm the only one interested maybe it's not worth the time.

As for the solution you propose it is cool imho: maybe in the very same "input" panel, by making shorter the white window with "input source / input target / autofire / #" and adding on top as the first line, above the device button, the thing that you said.

There should be a "compatibility" button still that prioritizes the choices in the "game & IO Ports" and that greys out the load-able custom configurations.

Maybe you could leave this one for future GUI' trimming, but if you can figure a clean implementation, it is imho a great add!