Empty file path means FC folder.FreeCommander.exe start FC with plugins and use FreeCommander.ini file
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Command line params /Ini, /NewIni
Command line params /Ini, /NewIni
Command line params:
Last edited by Alex on 21.10.2007, 17:18, edited 2 times in total.
[size=92][url=http://www.uvviewsoft.com]Universal Viewer[/url]
[url=http://www.uvviewsoft.com/logviewer/]Log Viewer[/url][/size]
[url=http://www.uvviewsoft.com/logviewer/]Log Viewer[/url][/size]
I support this request. It would be very useful when testing bugs with default settings and without plugins. I'm not sure how it should work exactly...
FreeCommander.exe should start FC with plugins and use FreeCommander.ini file and...
FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right? But when I change some option and start FC with the same parameters? New New.ini file will be created / old will be deleted?
If so, I suggest another parameter, because we need to use default settings, change few options and restart FC to test some bug, so here is my suggestion (I have changes New.ini to FCTest.ini, perhaps you can find a better name, it's not so important):
FreeCommander.exe start FC with plugins and use FreeCommander.ini file
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Of course, the new instance of FC should be started always.
I have a special FC folder to test bugs with default settings now, but I have to update both folders for each new version and delete the ini file often. With the suggestions above we could just create two shortcuts.
FreeCommander.exe should start FC with plugins and use FreeCommander.ini file and...
FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right? But when I change some option and start FC with the same parameters? New New.ini file will be created / old will be deleted?
If so, I suggest another parameter, because we need to use default settings, change few options and restart FC to test some bug, so here is my suggestion (I have changes New.ini to FCTest.ini, perhaps you can find a better name, it's not so important):
FreeCommander.exe start FC with plugins and use FreeCommander.ini file
FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Of course, the new instance of FC should be started always.
I have a special FC folder to test bugs with default settings now, but I have to update both folders for each new version and delete the ini file often. With the suggestions above we could just create two shortcuts.
Should use the New.ini, if it exists, or create new if it doesn't exist.FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right?
Like in TC.
Support!FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Yes, but we'd still have to enter that dir and delete the ini often, therefore my new suggestions.Alex wrote:Should use the New.ini, if it exists, or create new if it doesn't exist.FreeCommander.exe /I=New.ini /NoPlugins should start FC without plugins and create new New.ini settings file, right?
Like in TC.
Added in the (beta) test version, not released yet. Works perfect! Thanks Marek.Alex wrote:Support!FreeCommander.exe /NewIni=FCTest.ini /NoPlugins start FC without plugins and create always new FCTest.ini settings file (delete any existing FCTest.ini file before)
FreeCommander.exe /Ini=FCTest.ini /NoPlugins start FC without plugins and use existing FCTest.ini settings file
Closed.
Who is online
Users browsing this forum: No registered users and 34 guests