Menu/Save Options/to file : the_name_of_my_choice.ini, the_name_of_my_choice.tpl

[chroda]

I have as a practice to launch HFS by:
“C:\Program Files\HFS\hfs.exe” –a X:\save_HFS\yy.mm.dd.ini –i X:\save _HFS

I save the three fundamental files of HFS (.tpl, .vfs and .ini) in the directory “X:\save _HFS” in this manner :
The file .tpl and the file .vfs by the ini-commands contained in the file “yy.mm.dd.ini” :
load-tpl-from= X:\save _HFS\yy.mm.dd.tpl
last-file-open= X:\save _HFS\yy.mm.dd.vfs

and the file .ini by the command line parameter :
i X:\save _HFS

To do that, with the menu of HFS:
I can save the file .vfs like “yy.dd.mm.vfs” by:
Menu /Save file system…

and the file .tpl like “yy.mm.dd.tpl” by:
Menu / Edit HTML template… / Export

But I cannot save the file .ini like “yy.dd.mm.ini” while using: Menu / Save Options / to file ; indeed, the result is imposed in the form hfs.ini !
I must thus rename the file “hfs.ini” in “yy.mm.dd.ini” in the directory “X:\save _HFS”, which breaks the automation of this procedure…. 

I would thus wish for the file .ini the same type of safeguard as for the files .tpl and .vfs, thus ensuring a coherence in the safeguard of these three fundamental files.

is it possible to modify the menu "Menu / Save Options / to file" consequently ?


I hope that all that is clear . . . . !

Chroda

[Foggy]

Im not sure what your asking with the hfs.ini file is possible because when hfs launches it looks for a file called hfs.ini and if it doesnt find one it loads the default settings, so I tihnk that you'll have to ask rejetto about that one.

[rejetto]

what's the problem in renaming the file?
why you call it automation. if you click manually, it is not an automated procedure.

the problem in introducing such feature is that would confuse most people.
if you explain what's the problem in renaming, i can introduce a command line way to get a different name for the ini.