I exported settings from an installed version. On new laptop I don't have admin rights anymore so using the portable version, but Import doesn't do anything.
I don't mind re-entering settings manually if you explain how to read the dcs file. But I'd rather not tinker with it again to get eveything just right, how it used to be. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hello. thanks for the report and attached config file.
I looked into code and see no reasons why import doesn't work for this particular file (few my files I tested worked fine), but it does... I'm not surprised if it doesn't work on Windows due to Unicode symbols (Windows has eternal problems with Unicode in C/C++ apps), I tested it on macOS and was surprised that it doesn't work too! so, I setup dev environment on Linux and tested on it... and it works here! I have no clue what prevents settings import but assume this is somehow related to used Qt version. there is nothing related to file I/O and serialization on my side, I used Qt' mechanisms to save settings, just to keep code simple and do not invent some parsers/serializers. so, that's why .dcs files are unreadable.
right know I suggest you just replaces your settings.ini file in your portable version with file I attached, I build portable version for Linux and imported your settings. so, this file contains your settings, even clock positions for both screens. I tested it on portable Windows version, and it is loaded correctly.
one small thing I noticed in this config, you used some texture. path to textures are stored as absolute path, so you should change it according to new path to clock (or just select the same texture again and path will be saved).
despite on that project is closed, I'll investigate this issue, it is too strange
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't mind re-entering settings manually if you explain how to read the dcs file. But I'd rather not tinker with it again to get eveything just right, how it used to be. :)
I did have some unicode narrow spaces in the quick note, wonder if that's the reason.
Here is the export file. Appreciate if you could fix it for me so I could import most of the settings, if not all.
Diff:
hello. thanks for the report and attached config file.
I looked into code and see no reasons why import doesn't work for this particular file (few my files I tested worked fine), but it does... I'm not surprised if it doesn't work on Windows due to Unicode symbols (Windows has eternal problems with Unicode in C/C++ apps), I tested it on macOS and was surprised that it doesn't work too! so, I setup dev environment on Linux and tested on it... and it works here! I have no clue what prevents settings import but assume this is somehow related to used Qt version. there is nothing related to file I/O and serialization on my side, I used Qt' mechanisms to save settings, just to keep code simple and do not invent some parsers/serializers. so, that's why .dcs files are unreadable.
right know I suggest you just replaces your
settings.inifile in your portable version with file I attached, I build portable version for Linux and imported your settings. so, this file contains your settings, even clock positions for both screens. I tested it on portable Windows version, and it is loaded correctly.one small thing I noticed in this config, you used some texture. path to textures are stored as absolute path, so you should change it according to new path to clock (or just select the same texture again and path will be saved).
despite on that project is closed, I'll investigate this issue, it is too strange
SourceForge file attachment looks very strange: attached file is displayed not under message, but at the top of page... so I'll provide link to to the same file attached https://www.dropbox.com/s/dj9by6dvador5af/settings.ini?dl=1
Thanks so much for the ini file. The texture setting is from when I was experimenting. I am using a solid color actually.