You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @trzy , opening this ticket as requested in the forums.
Context:
During update, users tend to download the latest ZIP and simply overwrite all their old files with the new ones. Controller config is often cited as the part that needs work and having a Supermodel.ini included in the ZIP overwrites existing custom controls if users forget to back it up, which they will haha. Not a heavy task to back up, but an added cognitive load which users have to remember when doing so.
Proposed Solution:
For new users/fresh installs, the missing INI is not a problem because they are already instructed from the Help documentation to generate one if it is missing. Nothing changes from this POV.
For existing users with configs, the accidental overwrite is a real possibility. Removing the INI from future releases should require no additional code and Supermodel effectively behaves the same. All files are safely overridden on update, with the safety of avoiding a possibly frustrating mishap. This is the quick no-code solution.
Possible Approach: (good to have, not mandatory)
-config-inputs generates the INI if it does not exist. This is current behaviour, so no changes here.
-config-inputs detects an existing INI and asks the following in the cmd prompt:
Supermodel.ini exists. Do you wish to overwrite and reset inputs to default (y/n)? y
Creating new INI file...
(proceeds to the usual input config)
Supermodel.ini exists. Do you wish to overwrite and reset inputs to default (y/n)? n
Modifying existing INI...
(proceeds to the usual input config)
y = creates a new INI, all custom mappings reset to default
n = uses existing INI and appends to it, previous custom mappings preserved
The command is very well doing this now under the hood, but perhaps a couple of decision/confirmation messages further improves user experience when they are already daunted by the cmdline interface. This is also the feedback I hear from the emulation group I'm in, so I try to make the YouTube tutorials to make Supermodel config easier for them.
Thanks for reading Bart. Best of luck for your crunch time! :)
The text was updated successfully, but these errors were encountered:
Hi @trzy , opening this ticket as requested in the forums.
Context:
During update, users tend to download the latest ZIP and simply overwrite all their old files with the new ones. Controller config is often cited as the part that needs work and having a
Supermodel.ini
included in the ZIP overwrites existing custom controls if users forget to back it up, which they will haha. Not a heavy task to back up, but an added cognitive load which users have to remember when doing so.Proposed Solution:
Possible Approach: (good to have, not mandatory)
-config-inputs
generates the INI if it does not exist. This is current behaviour, so no changes here.-config-inputs
detects an existing INI and asks the following in the cmd prompt:y = creates a new INI, all custom mappings reset to default
n = uses existing INI and appends to it, previous custom mappings preserved
The command is very well doing this now under the hood, but perhaps a couple of decision/confirmation messages further improves user experience when they are already daunted by the cmdline interface. This is also the feedback I hear from the emulation group I'm in, so I try to make the YouTube tutorials to make Supermodel config easier for them.
Thanks for reading Bart. Best of luck for your crunch time! :)
The text was updated successfully, but these errors were encountered: