Several users who install any of the tweaks do not know how to utilise them when they first run the program.
The proposed solution is to store a value in the configs for all the tweaks that notes the last version of the tweak that was run, with the default being null. If the last version in the config does not match the current version of the tweak, the changelog and instructions should appear.
The changelog doesn't have to be massive, but it should indicate new end user features from the previous version.
The instructions should be at least enough to show the user how to enable the config window, how to perform some basic operations, and how to get help.
The window should also be available via a button near the bottom of the config window.
For Combo Indicator, a config will have to be made in order to remember whether the user has run the program for the first time.
Biendeo
commented
4 years ago
Several users who install any of the tweaks do not know how to utilise them when they first run the program.
The proposed solution is to store a value in the configs for all the tweaks that notes the last version of the tweak that was run, with the default being null. If the last version in the config does not match the current version of the tweak, the changelog and instructions should appear.
The changelog doesn't have to be massive, but it should indicate new end user features from the previous version.
The instructions should be at least enough to show the user how to enable the config window, how to perform some basic operations, and how to get help.
The window should also be available via a button near the bottom of the config window.
For Combo Indicator, a config will have to be made in order to remember whether the user has run the program for the first time.