Consequence of location of log files not uninstalled

[michelpons]

When uninstalling COLTT on a machine, and then re-installing the same version, the folder serving as location for the log files is kept. This is explicit when the folder location has been changed after the first installation. Uninstalling COLTT should not lead to deleting exiting log files for sure, but if the folder kept is not existing, it is not created after the second COLTT installation, leading to no log files being created anymore. Somehow a different strategy should be envisioned. For example, some check should be made after installation or during installation that the folder chosen exists and if it does not exist, the end-user could be asked to validate creation of the folder.

[michaelhalloran]

If there is no .ini file then COLTT will put log files in %LOCALAPPDATA%
CAPE-OPEN
COLTT Logs
If there is a .ini file then COLTT will use the value of log4j.appender.A1.File for the location of log files.
The .ini file is no longer installed at release 2.1, so in a clean installation COLTT relies only on its internal default settings. The intention is that a .ini can be written to override those only when needed.
Is this issue here that the directory referred to in a .ini file doesn't exist or that %LOCALAPPDATA%
CAPE-OPEN
COLTT Logs doesn't exist after the second installation?