In the next version, the default ini file location will be the wincmd-ini folder, and failure to (read or) write the file should no longer cause an exception.
Regarding to the location of the ini file:
I am using TC with different profiles. The ini files, called 'prof.ini' and 'newbie ini' are stored in a special folder called /tc/profiles/. Will there be any problem?
Should not be a problem; as "total-commander-ini-folder" I use the one I am told by TC itself in the FsSetDefaultParams function call. According to the interface description, that is always the same folder as the one where the wincmd.ini currently in use is located.
Should not be a problem; as "total-commander-ini-folder" I use the one I am told by TC itself in the FsSetDefaultParams function call. According to the interface description, that is always the same folder as the one where the wincmd.ini currently in use is located.
That's 100% correct! You should use this path, but may want to use a different file name than the one suggested, to have your own settings file not shared with any other plugins.
ghisler(Author) wrote:That's 100% correct! You should use this path, but may want to use a different file name than the one suggested, to have your own settings file not shared with any other plugins.
Yeah, I intend to use the path given in the FsSetDefaultParams function call, and name the file "tcburner.ini" as it is now.
