TOPIC:

How can I save the configuration file when updating to a new CT version? Sorry for my bad English and congratulations for your job.
Thanks

Having received no response I assume that we can not save the configuration files during the upgrade.
Thank you again

npda59 wrote: Having received no response I assume that we can not save the configuration files during the upgrade.
Thank you again

Npda59 has a valid point, and a much needed improvement it would be if configuration files could be saved over the installation.

Thanks

Guys
to find ALL Typhon configuration files
go to CTC-Folders page "Typhon 32 Settings" or "Typhon 64 Settings"
click to open the settings folder and backup what do you need.

but for more help my question is: What do you want to back up ?

For example, it would be very useful to be able to save the options in the Tools menu and the setting of the external tools

sternas wrote: Guys
to find ALL Typhon configuration files
go to CTC-Folders page "Typhon 32 Settings" or "Typhon 64 Settings"
click to open the settings folder and backup what do you need.

but for more help my question is: What do you want to back up ?

Those Typhon 32 and Typhon 64 Settings are exactly what we would like to have backed up and restored automatically. Because backing them up before installing is mostly forgotten.

On the other hand, this is not a trivial task. It is possible sometimes that changes in CT make some settings of the previous version invalid. Therefore an automatic save and restore of the parts that will remain valid after install is a good approach. The settings that cannot be restored, should be saved in a backup location for manual handling.

Case in point: the recent 4.70 release of CT changed the naming of a number of packages. Since these package names are stored in many files in the settings directory, just saving and restoring the directory contents does not work

In short, customizations to the IDE should be preserved as much as possible.

Serious request : as long as the update procedure nullifies all user customizations, actions like renaming packages should be avoided.

Hope this clarifies it