Hi, thanks for your question. Unfortunately, this seems to be some problem in your OS. Because we don't specify any permissions during file creation. We're using standard boost file system library for creating & copying the files.
Mentioned .bak
file is to protect your original file in case that save is interrupted by any way. Because of that we first create .bak file and when save is successful we remove .bak file.
For copying file from .skipper to .bak we're usign following routine (so as you can see no permissions are configured/changed):
boost::filesystem::copy_file(pathFromFile, pathToFile);
and for creating new files (.bak) we're using the following routine
//maped file params
boost::iostreams::basic_mapped_file_params<boostpath> mfp;
mfp.path = fileName.GetAsBoostPath();
mfp.flags = boost::iostreams::mapped_file::readwrite;
mfp.offset = 0;
mfp.new_file_size = lBufferSize;
//open and write to file
boost::iostreams::mapped_file_sink mf(mfp);
memory_trait::CopyMemoryBuffer(pBuffer, mf.data(), lBufferSize);
//close file
mf.close();
I believe that all files are created with permissions based on the user who run the application. Until now we don't receive any similar bug report, so I believe it has to be by some configuration on your side.