A while back, I wrote:
Quote:Problem is, I use a good number of different .ini files for different reasons, mainly due to different screen resolutions, so editing the .ini file each time could get confusing.
Here's something I've noticed. One of my shortcuts has this as a property:
Quote:C:\Sesame\Program\sesame.exe -ini_file C:\Sesame\1150-950-sesame.ini
This has a "Start In" value of C:\Sesame. The "1150-950" represents the dimensions of the Sesame window which opens.
When clicked, Sesame starts fine, and uses the screen dimensions specified in 1150-950-sesame.ini. However, when I use the application utility to redesign the application, it uses the "Load data on redesign" switch specified in the sesame.ini file located in C:\Sesame, ignoring the specification in 1150-950-sesame.ini.
I have several such .ini files which set different window dimensions. However, no matter which shortcut I use, they always set the screen dimensions specified in the shortcut's command string, but use the "Load data on redesign" switch specified in C:\Sesame\sesame.ini.
This, of course, solves my problem of having to edit multiple .ini files if I want the redesign to include data or not, but begs the question of which .ini file is actually controlling the process. Any thoughts?