Robert You ask for ideas/contributions and then dismiss them all (well all but the one about the FSPEC line). Let me see now...
RE: Decouple the 'FilePath' entry from the most recently used path. You said:
==> When you pick a path, that becomes the 'root' of your file activity. Why shouldn't that become the FilePath?
Answer: Yes and No! I may have many edit tabs open. Why should their contents all come from the same path?
Example: I'm working on some source code. It may have many modules stored in a common path, Emphasis on MAY!. Some may not be in the same folder.
So I enter the FilePath once (although more likely it'll be my 'Recent Paths' list anyway 'cause I keep the ones I access most frequently).
While working through various modules I briefly need to access something else, most likely in my case via my 'Recent Paths' list.
For a quick peek at something else, I now have to re-enter the FM FilePath because a brief diversion changed it. POO!
No I don't want ANOTHER FilePath and it doesn't take multiple FMs to do what I ask.
All I'm asking is that the FilePath value, as shown on the FM FilePath tab, stay as I entered it, instead of reflecting wherever the most recent file accessed via SPFLIte resides.
If you want to get real fancy with it, how about the value on the FM FilePath TAB reflects the path for whichever EDIT TAB I used most recently?
RE: FLISTS
You said:
===> SURE you can edit the FLISTS from there. Go the FLIST tab, pick the FLIST you want to edit, and put an E line command on it.
Answer: Amazingly I've never entered an "E" or "S" line command on any FM page!
I understood that in FM, clicking on the entry was the same as entering 'S' as a line command.
I just click on the entry, because my hand is already on the mouse, having just clicked the FM Tab header.
The FM 'FLIST' Tab, simply shows a bunch of FLIST files. In that respect it is no different to, say, the RECENT Tab, which shows a bunch of files.
Have you tried clicking on the 'Recent Paths.FLIST' entry? How about 'S' next to the 'Recent Paths.FLIST' entry?
By the way, my RECENT PATHS.FLIST content doesn't change. That's good, I like it that way. Plse don't change that!
But given that behaviour, would "FREQUENTLY USED PATHS.FLIST" be a better name?
Re FAVOURITES.FLIST
You said:
===> It is conceivable that you might want a "most frequently edited" list,
Answer. No, 'RECENT' does that job. Please don't speculate.
RE: Max No of entries for each FLIST
This is useful is because I may well want to save a lot of 'FAVOURITES' or 'RECENT PATHS' entries but I do not want SPFLIte to save a huge list of 'RECENT' entries.
The OPTIONS panel describes it as "Number of entries in recent lists". Note the use of plural in 'lists'. I assume therefore it applies also to RECENT PATHS.
And the reasons why a long 'RECENT' list is a pain in the rear is because the longer the list...
- the less useful it is as the older files clutter things up, regardless of Date sorted order
- and, more importantly, the greater the chance that it will contain files stored on 'semi-online' devices and therefore HUGELY DELAY SPFLite startup!
I appreciate 'semi-offline' isn't a common term - I use it to describe a device that is Online, but asleep.
SPFLite just ignores files on OFFLINE storage, but for ONLINE but ASLEEP storage, it waits (not SPFLite's fault) for the device to wake up.
And this delay applies at startup, not when you access the file.
George and I have already discussed this and it cannot realistically be fixed 'cos Windows issue no notification to SPFLite that a delay is to be expected.
Is there a problem. Doing either switches to Recent Paths mode, what did you expect? (Edit?)
