Page 1 of 1
The "xnconvert.ini" file
Posted: Tue May 24, 2011 10:01 pm
by budz45
Hi again,
I propose either one of the following two things:
1.) If the 'ZIP' downloads of XnConvert could ship with the .ini file already in the folder (portable ready)
OR
2.) If XnConvert, upon first ever launch, could ask the user in a prompt window where they want settings to be saved to.
Re: The "xnconvert.ini" file
Posted: Thu Jun 16, 2011 8:15 pm
by budz45
budz45 wrote:
2.) If XnConvert, upon first ever launch, could ask the user in a prompt window where they want settings to be saved to.
Like how some apps ask if they want to save to
a)
application data
b)
program folder (portable app)
..Then user would select either one.
Re: The "xnconvert.ini" file
Posted: Sun Jun 19, 2011 4:30 am
by vaejiofr
budz45 wrote:
1.) If the 'ZIP' downloads of XnConvert could ship with the .ini file already in the folder (portable ready)
What I don't like about that is you have to be careful not to overwrite your ini file when updating. There's two solutions for this:
1. Store the settings in a sub-folder. The zip archive contains this folder, but it's empty so no files are overwritten. If the folder exists, then XnConvert runs in portable mode.
2. Create a separate "portable" file. If the file exists, then XnConvert runs in portable mode.
Re: The "xnconvert.ini" file
Posted: Wed Jun 22, 2011 2:48 pm
by budz45
vaejiofr wrote:
2. Create a separate "portable" file. If the file exists, then XnConvert runs in portable mode.
Hmm I like this suggestion

and this "portable" file would tell XnConvert to create and write to an .ini in same folder

(like how portable foobar2000 does this).