Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 24, 2015 1:28:25 GMT -5
Hi,
If I forget to create the directory OPTIONS in c:\temp
then
spflite.exe -INIT "c:\temp\OPTIONS\spflite.INI"
will go into a infinite loop.
Jonas
|
|
|
|
Post by nicc on Jun 24, 2015 4:15:59 GMT -5
I don't understand this - I have never created an OPTIONS folder for SPFlite - nor does one appear to exist on my machine. SPFLite.ini lives in C:\users\myid\documents\spflite
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 24, 2015 9:29:30 GMT -5
I read this in the documentation and then I tried it.
From Documentation:
-INIT option
The -INIT option causes SPFLite use a different INI file for customization, instead of SPFLite.INI. This allows you to have INI files with different global options such as handling of file deletions, fonts and screen colors, mouse and keyboard options, etc. (Note that keyboard mappings are held in the SPFLite.KBD file, which cannot be overridden like the INI file can.)
To use, add -INIT initname to the command line, where initname is either:
- the base name of the alternate INI file. For example, to start SPFLite using an INI file named CUSTOM.INI the command line would be -INIT CUSTOM. The INI file will be searched for in the normal SPFLite data path (Documents\SPFLite).
- A fully qualified path to the INI file. Example: -INIT "D:\Data\Editors\SPFLite\CUSTOM.INI"
|
|
|
|
Post by nicc on Jun 24, 2015 10:31:59 GMT -5
If you really want a temporary .ini file executed from a temporary folder then why not use a .bat file to create your temp folder, copy your .ini file from wherever it is (and why not use that location?), execute SPFLite and, finally, delete the temporary folder?
|
|
|
|
Post by George on Jun 24, 2015 10:54:04 GMT -5
Jonas: I'll have a quick look for the loop problem. Originally, many, many versions ago, we did not even have separate Profiles based on file type, we did not have a separate KBD file for key customizations, etc. EVERYTHING was kept in the main INI file.
Thus the need for alternate INI files. Thinking about this now, I'm not sure there is any requirement left at all that justifies carrying this support forward.
Comments anyone? Is this even remotely needed anymore?
George
|
|
|
|
Post by Jo on Jun 24, 2015 11:13:06 GMT -5
Ah, yes I remember: more than 3 years ago, I had seperate .INI-Files for some totally different projects, each with other startup-directories and other filemasks. FM in SPFLite at this time was rather rudimentary, and there were no FILELISTs. Now I use just the standard .INI-file. I love the FLISTs ;-) !
Jo
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 24, 2015 15:15:40 GMT -5
I don't need this feature.
Jonas
|
|
|
|
Post by George on Jun 24, 2015 15:37:51 GMT -5
My suspicion is that this can be yanked, with nil impact to anyone.
George
|
|
