|
Post by TheFeDuke on Feb 8, 2016 17:12:38 GMT -5
I'm not entirely clear what's wanted here. Me, too. I thought that I was trying to offer a contribution on the remote chance that it might help someone, not raise an issue or enhancement request. Now that I have been thought provoking, I see that you want to help, too. Discussion is good. When files can't be reopened, because of a drive letter change, can the previous SPFLite drive be saved, with option to translate the drive letter of previously opened files to the current SPFLite portable drive if they are the same as the previous SPFLite location? An example might help. I run SPFLite Portable on system 'A' from drive 'K:' and SPFLite remembers. I open files on drives 'K', 'G' and 'C', leaving them saved and open when I exit. On to system 'B' where the portable media is referenced as 'J'. Before SPFlite looks to save the information that it is running on 'J', an inconsistency is detected with the previously stored SPFLite location. Coincidence will dictate the previous activity for files on 'G' and 'C' as it does at present, but there is now an opportunity to translate the 'K' files to 'J' before opening and saving 'J' as the new 'last run from' drive letter. What might you think of that? Just to mention that I avoided using using SUBST in my solution to assign a consistent drive letter on different systems because of other considerations. Regards,
|
|
|
Post by TheFeDuke on Feb 8, 2016 11:57:57 GMT -5
On that thought, one message, stating that "a number" of previously open files are missing would reduce traffic. I did use the individual messages to note what files I could re-open. I don't see much value there.
This sort of .ini file manipulation takes care of the system specific settings and as such has no use in the system installed SPFLite, except for history data. I just got intrigued enough to pursue a pre-process to communicate data with my Windows XP back-level SPFLite. The above scheme does support three-way sharing using the back-level portable version.
|
|
|
Post by TheFeDuke on Feb 8, 2016 2:20:44 GMT -5
I do most of my editing on removable media on a desktop and laptop with different screen sizes, resolutions, font sizes and drive letters. My feeble eyes seek maximum readability. The open tabs don't travel well on different drive letters when I move outside in good weather. I use a desktop shortcut to a batch startup script on my flash drive using a working directory pointing to my data in a minimized window. Here is the batch script:
SetLOCAL EnableDelayedExpansion Set "Drive=%~d0" Set "DriveLetter=%Drive:~0,1%" Set "PortableSPF=SPFLite.V8.3.6022" PushD %Drive%\%PortableSPF%\Config >nul Copy SPFLite_Drive%DriveLetter%.INI SPFLite.INI PopD Call "%~d0\SPFLite.V8.3.6022\SPFLite.exe" PushD %Drive%\%PortableSPF%\Config >nul Copy SPFLite.INI SPFLite_Drive%DriveLetter%.INI PopD pause
The name of the portable SPFLite directory is a variable and the drive letter is determined by the location of the batch script. SPFLite.ini is restored to its state at last use on this PC and is harmless on first use. SPF starts and can use the working directory for the RUN command. SPFLite.ini is saved after SPFLite exits. If SPFLite does not terminate properly or the startup window is closed while SPF is running, the saved .ini will not have the most recent session changes. If SPF is started normally the saved .ini is not referenced during that session and the next startup shortcut will not reflect that activity.
This won't appeal to a large audience, but it saved me lots of OPTIONS commands and error messages opening non-existent tabs. Regards, John A.
|
|
|
Post by TheFeDuke on Dec 12, 2015 15:54:27 GMT -5
If you'd like a corrected version prior to the next release, you can download it Thank you, George. That works great now. I got that, Robert. My power machine is the Win 7 Desktop and I have a Win 7 Laptop with a damaged keyboard and forgotten password that I salvaged from an acquaintance that I use in good weather out on the porch. I am too cheap to discard the XP but I can make it Wifi movies to my TV while I work on the other. That leaves a question. When upgrading my 8.3 version, do I rebuild the portable each time or can I apply the downloaded setup program to the removable media folder directly? Regards,
|
|
|
Post by TheFeDuke on Dec 12, 2015 2:32:06 GMT -5
Hello, again.
I have been going portable for some time now, but I have not been able to move past Ver 8.2. I am using the same technique as in the help, but my options.ini keeps been accessed from the SPFLite folder in Documents and not the Config folder on the memory stick. The changes.txt does not describe withdrawal of the portable option and I really like the feature. I have updated, uninstalled, reinstalled and rebuilt portable versions of both 8.3 versions. They all function but are not really portable and collide in one documents folder.
During my experiments, I created a V8.3.5295 portable setup exhibiting non-portability. I then copied SPFLite.exe from my working V8.2.5179. This made it point to the Config folder for OPTIONS, naturally exhibiting a .kbd incompatibility. From this, I am inferring that the 8.3 SPFLite.exe files have dropped the logic to check for the presence of the Config folder.
At the moment, I am running functionally stabilized SPFLite V8.2 (system and portable) on my functionally stabilized Win XP system, system V8.3 and portable V8.2 on a Win7 laptop system and pseudo-portable V8.3 with no system SPFLite and portable V8.2 on a Win7 desktop system. When I get rolling, I have colorized shortcut icons and window icons for my SPFLite and DOS Prompt testing windows with matching SPFLite FM color bars and quoted text coordinated with the physical color of my memory sticks. This helps me to keep oriented when bouncing among the windows.
Please set me straight if I missed something. I can zip an SPFLite folder and post a cloud link if need be.
Thanks, (the unbalanced colorize guy),
|
|
|
Post by TheFeDuke on Aug 15, 2015 17:53:01 GMT -5
Hi Folks. It's all good. Language blind is good. I was just explaining why it occurred. I'll go back to figuring out how to colorize out the end of some language specific end of comment situations. You probable already have the features that I just need to define. Please note that I balanced the quotes in the above paragraph. Cheers!
|
|
|
Post by TheFeDuke on Aug 15, 2015 1:32:53 GMT -5
Thank you, George. So it is an interesting coincidence that I once affected to use a ' to begin some of my file and environmental variable names for convenience in collating order and that I could use a "set '" command to check on things. There is no unbalanced quote in either " Set 'var=String " or " Echo.%'var% ", but I can see how that could come up when looking at such code. Once again, My compliments on your product and responsiveness.
|
|
|
Post by TheFeDuke on Aug 14, 2015 12:44:23 GMT -5
Thanks, gentlepeople. Just to put it into perspective, very low priority on my part. I am OK with the workarounds for now, so do what you do in due course or in case this is the tip of some iceberg that might affect others. Social: Burlington to North York. I was always lucky enough to live east of work. no solar glare from Pickering.
|
|
|
Post by TheFeDuke on Aug 14, 2015 2:00:29 GMT -5
From SPFLite.ver: 8.2.5179 EXE HILITE AUTO OFF made the displayed text grey and removed the two bytes. Interestingly enough they are also removed by minimizing and restoring the window and by covering it with another window and popping it to the foreground again. I have attached bat.AUTO and a dull sample file called overbyte.bat, if I understood how to use the forum attachment tool. If nothing else, I now have a couple of workarounds. Environment: I started with SPFLite about two years ago on a reclaimed blue screen of death XP system and then used it on a refurbished Windows 7 system and a flash drive which I did not (as I learned later) set up properly until recently, by which time I was on Windows 10. Regards, Attachments:bat.AUTO (2.31 KB)
OverBite.bat (2.05 KB)
|
|
|
Post by TheFeDuke on Aug 12, 2015 23:53:30 GMT -5
I developed a readability problem in edit since the update that corrected the FM display problem that left the last file acted on in the next page scrolled. Two bytes are displayed at the end of the data of some lines in Edit. I discovered that is was not arbitrary but occurred after scrolling to a relatively short line in the same position on the second page as a longer line in the previous page. [Pg Dn] and [Pg Up] and the two bytes cleared if the next page contains white space in that position or are replaced with two bytes from that position on the third page. The data is fine, but the display is very confusing. The [End] key positions to the beginning of the garbage, which reacts strangely to deletion and over-typing. I edit mostly .bat files using colorization. Perhaps I am missing some setting that was sensitized in that update.
Your product is wonderful. All of my old tricks work great! Waxing nostalgic, I worked at 243 Consumers' Road when it opened in the 70's.
Regards,
|
|