|
Post by TheFeDuke on Apr 26, 2016 13:23:17 GMT -5
Excellent. I like that much better. One size fits all at the beginning and the examples at the end of the options descriptions demonstrate their use. Smooth. You know how to do what I should have meant instead of what I said.
John A.
|
|
|
Post by TheFeDuke on Apr 25, 2016 14:18:23 GMT -5
In 'Forum > Problems and Bugs > Behavior of '-INIT' command line option', I mentioned: to which George replied: So now might be a good time to amend the help section of "-INIT option" in "SPFLite Command Line Options" within "Starting and Ending SPFLite" under "Working with SPFLite" to something like:
can now Drag-and-Drop files onto the icon to quickly View them. < insert line > -INIT option < insert line > The -INIT (or any abbreviation down to -I) 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:
o 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). o A fully qualified path to the INI file. Example: -INIT "D:\Data\Editors\SPFLite\CUSTOM.INI" < insert line > -KEYMAP option < insert line >
It currently reads something like:
can now Drag-and-Drop files onto the icon to quickly View them. -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:
o 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). o A fully qualified path to the INI file. Example: -INIT "D:\Data\Editors\SPFLite\CUSTOM.INI" -KEYMAP option That should improve readability and document the short form as it is for the other options. I should have mentioned this in a Documentation Topic in the first place.
Regards, John A.
|
|
|
Post by TheFeDuke on Apr 9, 2016 14:09:36 GMT -5
Good job again, George. Naturally, I was just about to post my detailed test results, monitoring MRFList= to try to help, but you beat me to it. Oh, please don't turf it. I intended to rescind one of my really ugly contributed files that renamed INI files in deference to a properly working -INIT option.
I think I tried to explain this a while ago, but you asked and you have spun wheels so many times to help me that you deserve it.
This all has to do with my cataracts and two Windows 7 systems. They have radically different screen sizes and resolutions. Although I work best on the desktop with the 22" monitor, I prefer working in the fresh air on the porch in good weather using my laptop with the small screen. All of the data that I use with SPFLite is maintained on two memory sticks which I keep current using FreeFileSync from SourceForge tools. I found INI files customized to the drive letters on the two systems works very well for continuity and bringing up SPFLite with the appropriate font sizes.
The other big factor is that I rely quite heavily on colorization to keep myself oriented to what I am doing, so I have colorized my File Managers differently for system-installed and portable versions: Neutral for host, orange and magenta for the removable media. In addition, all quoted text being edited is colorized in a similar way. This was less clumsy for me than using the cloud where I had too much trouble keeping things straight.
I could fix this all by acquiring a good gaming laptop with a large screen, but that is not to be. Throw in the old XP system which still runs SPFLite 8.2 for good measure and there is a lot to keep organized.
So it is a combination of budget, hardware, personal habit, my ducking senior moments, poor eyesight and an increasing dependence on your wonderful product that makes me one of your strangest and more demanding users.
John A.
|
|
|
Post by TheFeDuke on Apr 8, 2016 12:46:54 GMT -5
George, I tested using these commands alternately, each time ending SPFLite, after opening an edit tab from FM, by closing SPFLite, clicking the close "X" box in the top right hand corner:
Start "" "C:\Program Files\SPFLite\SPFLite.exe" -I "C:\Users\Jani.Bride\Documents\SPFLite\SPFLite.INI" Start "" "C:\Program Files\SPFLite\SPFLite.exe" I noticed the problem using other INIs but this was the best way to demonstrate it.
John A.
|
|
|
Post by TheFeDuke on Apr 8, 2016 1:19:16 GMT -5
I am sorry that I did not pick this up before the last release. The -INIT argument now works both in the detailed and short specifications as well as in both system and portable usage. There is, however a difference in the way previously opened file(s) are handled. The file manager is opened to the last used path, but the previously opened file(s) are not opened if -INIT is specified. I tested using SPFLite.INI being specified and being defaulted. Previously opened files always worked when -INIT was not used, even if the previous session was ended with open files in a session that specified -INIT.
John A.
|
|
|
Post by TheFeDuke on Mar 19, 2016 18:24:05 GMT -5
Attached is a text file containing the March 21, 2016 Version of the batch script of the subject of this forum topic.
[Edit: Attachment removed Mar. 29, 2016. The most current version is in the first post in this topic.]
You can write 'system. ini' or 'system .ini' but if mentioned without the space the phrase cannot be mentioned, even in prose, anywhere in a post or the censure attacks. The offending code has been altered to accommodate ProBoards security reservations on the content.
John A.
|
|
|
Post by TheFeDuke on Mar 13, 2016 0:49:02 GMT -5
George, I have made you anonymously famous. My problem in supporting my contribution on your PC system is solved. I refer you to: DIR output format depends on Region and Language settings.I shall apply this fix to the code in the first post. In the meantime, if you are curious to see it on your system, you can temporarily set the time formats in the Region settings of the Control Panel from 'hh:mm:ss' to 'hh:mm:ss tt' to try it as-is. Still accepting, if not welcoming as much, problems. Still accepting, but welcoming more enthusiastically, suggestions and discussion, John.
|
|
|
Post by TheFeDuke on Mar 9, 2016 12:43:07 GMT -5
There is a batch script version update in the first post and here is somewhat more dramatic output:
|
|
|
Post by TheFeDuke on Mar 7, 2016 10:19:00 GMT -5
I guess that because my %UserProfile% is too long, the actual filename and extension of the .INI file is obscured in the 'INI File is:' display box of the 'SPFLite Global Options' dialog window. The field is left justified. If it were right justified, much like the 'Target:' box of the Shortcut Properties dialog box, that important part would be visible. Alternatively, if the 'Cancel' and 'Done' boxes were side-by-side instead of up-and-down there would be more room to display the whole field. My requested priority on this is zero, unless you like the idea.
Related to .INI files, I plead guilty to giving in to curiosity and experimenting with the contents and will share my observations. I found two places where I could insert free-form comments that appear not to interfere with .INI file processing by SPFLite and that survive updates both by regular activity and the use of the 'options' command. I can display any such documentation using the FINDSTR batch command. I am OK with that, but seek your blessing/comments/cautions on such practices. Here are my hacks. They can be placed after the 'Build=' statement between the [System] and [Manager] tags. I also added a [Comment] tag and free-form text at the very end after [Mouse] and its keyword with no ill effects. Interesting!
So, naturally, I thought of the 'Comment:' box of the Shortcut Properties and room for a 'Comment' tab just crying to be filled in the 'SPFLite Global Options' dialog window using the latter method to title a new tab. User customized comments in INI! That also demands zero priority unless you are inspired by such an idea.
|
|
|
Post by TheFeDuke on Mar 5, 2016 13:41:53 GMT -5
Here is one of my crash files:
SPFLite has encountered an execution exception (C0000005)
Last Interactions were: KB Primitive: ENTER Line Cmnd: D Primary Cmnd: END
Module Back Trace: 00 | DISPSCREEN
Note: A copy of this message is in: C:\Users\Jani.Bride\Documents\SPFLite\SPFLiteCrash.txt
I know that the date and time of the crash can be determined by the creation time of the file, but you have taken the trouble to put the name of the file after 'Note:' when it also is available by looking at the name of the file.
Would it not be useful to add the date and time to the note? Hopefully trivial?
|
|
|
Post by TheFeDuke on Mar 5, 2016 0:14:14 GMT -5
I am having difficulty in using the base name of an alternate INI file when starting SPFLite by command. First, I have a documentation comment. I inferred the use of this option from the example. For the example to work, the SPFLite program folder must be in the Current Directory or in the PATH. I only attempted using CD. The example used the form '-I'. I noticed that for '-BROWSE' and '-VIEW', help describes short form usage, but not for '-INIT'. Here is my test run: C:\Users\Jani.Bride>PushD "C:\Program Files\SPFLite"
C:\Program Files\SPFLite>Dir "SPFL*.exe" Volume in drive C is Windows Volume Serial Number is 4479-1C9B
Directory of C:\Program Files\SPFLite
01/23/2016 12:56 PM 432,128 SPFLite.exe 12/03/2015 02:24 PM 429,568 SPFLite.V8.3.5337.exe 01/23/2016 12:56 PM 432,128 SPFLite.V8.3.exe 02/22/2016 01:40 PM 431,616 SPFLite.V8.4.6026.exe 02/24/2016 03:50 PM 432,128 SPFLite.V8.4.diags.exe 02/22/2016 01:40 PM 431,616 SPFLite.V8.4.exe 02/24/2016 02:54 PM 432,128 SPFLite84.beta2.diags.exe 03/01/2016 12:22 AM 431,616 SPFLite84.exe 8 File(s) 3,452,928 bytes 0 Dir(s) 63,575,760,896 bytes free
C:\Program Files\SPFLite>Dir "C:\Users\Jani.Bride\documents\SPFLite\*.ini" Volume in drive C is Windows Volume Serial Number is 4479-1C9B
Directory of C:\Users\Jani.Bride\documents\SPFLite
03/04/2016 12:50 PM 2,244 SPFBeta.INI 03/04/2016 06:27 PM 2,290 SPFLite.INI 2 File(s) 4,534 bytes 0 Dir(s) 63,575,760,896 bytes free
C:\Program Files\SPFLite>Call SPFLite somenew.txt
C:\Program Files\SPFLite>Call SPFLite -I "C:\Users\Jani.Bride\documents\spflite\SPFlite.ini" somenew.txt
C:\Program Files\SPFLite>Call SPFLite -I SPFLite somenew.txt
C:\Program Files\SPFLite>Call SPFLite -I "C:\Users\Jani.Bride\documents\spflite\SPFbeta.ini" somenew.txt
C:\Program Files\SPFLite>Call SPFLite -I SPFbeta somenew.txt
There are five CALLs to SPFLite after setting up and describing the environment: - Worked as expected and opened the text file tab.
- Worked as expected and opened the text file tab. Used correct .INI .
- Started Default INI dialog for new installation and then opened the text file tab. 'opt' command showed INI file is: 'SPFLite'. (no path information)
- Worked as expected and opened the text file tab. Used correct .INI .
- Started Default INI dialog for new installation and then opened the text file tab. 'opt' command showed INI file is: 'SPFbeta'. (no path information)
I never did find out where the newly create INI files went. It is interesting to note that the INI box showed showed no .INI extension. Moreover, the Current Directory got filled with this clutter: Command > Scroll > CSR
_ New _ FilePath _ Recent _ Found _ Opened _ Favorites _ Flists _ Paths _ Profiles File Path/Name> C:\Program Files\SPFLite\ File Patterns > * Cmd Dir+ Name Date- Size _____ ..\ _____ VSAVE\ 2016-03-04 12:40 _____ THEMES\ 2016-03-04 12:40 _____ STATE\ 2016-03-04 12:40 _____ RUN\ 2016-03-04 12:40 _____ PROFILES\ 2016-03-04 12:41 _____ MACROS\ 2016-03-04 12:40 _____ Lib\ 2015-12-12 18:01 _____ JOBS\ 2016-03-04 12:40 _____ Filter Examples\ 2015-12-12 18:01 _____ FILELIST\ 2016-03-04 12:40 _____ CLIP\ 2016-03-04 12:40 _____ AUTO\ 2016-03-04 12:40 _____ SPFLite.SPR 2016-03-04 12:41 98 _____ SPFLite.ver 2016-03-04 11:20 14 _____ SomeNew.txt 2016-03-04 11:07 32 _____ SPFLite84.exe 2016-03-01 00:22 431,616 Line Commands: Add to favorites Browse Clone Delete DIR Edit EXclude
The uniform creation times show all of the signs of a new installation that should be in the Documents folder where SPFLite should have looked for the INI file, not the system SPFLite program folder.
|
|
|
Post by TheFeDuke on Mar 4, 2016 20:19:05 GMT -5
George, FYI, it is the system command CHOICE.EXE that is issuing the error message, complaining of my bad input. I have been working on this quite a bit and expect to upload a new version soon. [Edit: New version of code is in the first post.]
Meanwhile, would you please send me the output of a 'SET' command so that I can see if I am using the correct system variables. Is your Windows 10 system native or upgraded from Windows 7 or 8?
When you mentioned that you keep SPFLite versions in your Documents folder, does that mean that has all of the files normally found in \Program Files (x86)\SPFLite\, including the SPFLite.exe, kind of like the early step in creating a portable version, but without the \config manipulation? I set one up in anticipation. [Edit: Upon rethinking, a full portable seems more likely. To restate the question, are the .INI files shared with the system or in \Config in those documents program folders? ]
I was on all afternoon and am sorry that I missed your reply earlier. It was updating the hours since my last post and I did not notice yours until I refreshed the webpage.
|
|
|
Post by TheFeDuke on Mar 3, 2016 16:12:11 GMT -5
I corrected a typo in the first post. Line 32 should read:
If "%ProgramFiles(x86)%" NEQ "" Set bit64="%ProgramFiles(x86)%\SPF*" It did read (x64), so the script only worked on 32bit systems. George, the way that you did set up, you should be able to double-click or open that desktop file as well as using the DOS prompt after you make the change.
|
|
|
Post by TheFeDuke on Mar 3, 2016 13:42:42 GMT -5
Thank, you, George. That's just the quick try that I was looking for. I have some changes, anyway. Until then please paste the contents of 'Target:' box of the shortcut properties of both the shortcut to your SPFLite shortcut and the one to my batch script into a reply. For now, the passing of SPFLite arguments needs some work on my part and I'll be raising a bug report on '-INIT' handling. I had problems before, but now I have a good test vehicle to document them.
|
|
|
Post by TheFeDuke on Mar 3, 2016 1:50:01 GMT -5
Here is a batch script to start SPFLite from a DOS prompt [Edit: ,Shortcut or desktop .bat]. It requires no arguments and searches for SPFLite installation folders to present a menu that can include portable versions. A choice will then present any program versions within the selected folder if applicable. Any startup option arguments that are specified are passed to SPFLite as-is. Defaults are provided and automatically selected when no choices are available. This script can be executed from anywhere and has no installation process or dependencies. If run from removable media, it searches for portable versions only on the root of that drive. [Edit: as well as the SPFLite system install and user Documents folders.] It uses commands that are not available on Win XP and has only been tested on 32- and 64-bit Windows 7. [Edit: Here is representative output run from a desktop batch script on 64-bit Windows 7 system]: (There is also a screenshot in a later post.)
SPFLite program folders found in 'C:\Program Files (x86)' '1' C:\Program Files (x86)\SPFLite '1.1' (01/23/2016) SPFLite.exe '1.2' (12/03/2015) SPFLite.V8.3.5337.exe '1.3' (01/23/2016) SPFLite.V8.3.6022.exe '1.4' (03/01/2016) SPFLite84.exe '0' C:\Program Files (x86)\SPFLiter' Contains no SPFLite programs '0' C:\Users\Zani\Documents\SPFLite' Contains no SPFLite programs
SPFLite program folders found in 'C:\Users\Zani\Documents' '2' C:\Users\Zani\Documents\SPFLite.V8.4.6026 '2.1' (02/22/2016) SPFLite.exe '2.2' (02/22/2016) SPFLite.V8.4.Beta.exe '2.3' (12/12/2015) SPFLite_V8.3.5295.exe '2.4' (03/01/2016) SPFLite84.exe
(Default:'1') Choose from the program folders above: [1,2,C]?1
Selected: C:\Program Files (x86)\SPFLite
SPFLite program Versions found in 'C:\Program Files (x86)\SPFLite' '1' (01/23/2016) SPFLite.exe '2' (12/03/2015) SPFLite.V8.3.5337.exe '3' (01/23/2016) SPFLite.V8.3.6022.exe '4' (03/01/2016) SPFLite84.exe (Default:'1') Choose from the program versions above: [1,2,3,4,C]?1
Selected: SPFLite.exe
SPFLite .INI Versions found in 'C:\Users\Zani\Documents\SPFLite' '1' (03/07/2016) SPFLite.INI
Automatic selection made.
Selected: SPFLite.INI
Start "" "C:\Program Files (x86)\SPFLite\SPFLite.exe"
Enter 'EXIT' to end dbl-clk window... Edited: Attached please find the code for the batch script in text form for downloading. Name it as you wish with an extension of '.bat' but the code is sensitive to the first label remaining as ':FindSPF'. FindSPF.txt (25.83 KB) I would appreciate feedback on how it performs on other Windows 7 systems and, of course Win 8 and 10. I shall post some of my known limitations and naming assumptions if there is any interest. [Edited: A code preview of Version updated 3/29/2016 in the above attachment follows:] @Echo Off @Echo Off rem. READ ME - If this is distributed as a .txt file, rename to a .bat file after download. :FindSPF Version 2.1 03/29/2016 Fix - Generalize determining Documents Folder Rem.FindSPF Version 2.0 03/21/2016 Fix time/.ini and support SPFLite 'RUN' command Rem.SPFedit Version 1.5 03/20/2016 mitigate Regional time display format Rem.SPFedit Version 1.4 03/10/2016 added current version display Rem.SPFedit Version 1.3 03/09/2016 added double-click ending and argument passing Rem.SPFedit Version 1.2 03/07/2016 added .INI selection before starting SPFLite Rem.SPFedit Version 1.1 03/05/2016 added program version display for system SPFLite Rem. Author - John Andrejsons - accepting PM to user: thefeduke at DOStips forum Rem. acknowledges code and influences from DOStips.com and its forum Rem. http://spflite.freeforums.net/thread/244/spflite-command-supports-versions-options
John A.
|
|