|
Post by George on Mar 28, 2021 11:52:05 GMT -5
Robert: Stefan: You can tell it's a quiet Sunday.
New Beta posted (21087)
CUT and CC commands allowed in FM. Most normal CUT operands allowed (APPEND, NEW, RAW, named-clipboards), but not the non-aplicable ones like (line-range, X/NX, U/Nu etc.)
RUN opened up for CLIP sessions, treating it as a .BAT file type.
FM Line command CLONE/C renamed to KLONE/K.
George
|
|
|
Post by Stefan on Mar 28, 2021 13:04:18 GMT -5
George,
Just in case it is relevant - I use RUN regardless of file type. Windows figures it out according to the .EXE associated with the filetype.
So it it's a .BAT file, it runs as a BAT file in the CMD shell. If it's a REXX routine, it runs as a REXX file in CMD window (.REX is associated with the REXX shell command) If it's a .TXT file and you RUN it, a CMD shell window appears but the .TXT file is loaded into NotePad as usual. In each case you need to EXIT the CMD shell bedore you return to SPFLIte
Great when testing stuff as you don't need to save the changes first.
|
|
|
Post by Stefan on Mar 28, 2021 13:10:40 GMT -5
George RE: CEND I'm a creature of habit. PFK3 has returned me from whatever I am doing to whatever I was doing before for decades. Thus my fingers automatically hit PFK3 (END). I even mapped PFK4 to !=X because, back in the day, that's how I exited ISPF. And my fingers still do that to close SPFLIte I figured a separate command wouldn't be hard, given that the macro isn't exactly taxing. And it leaves it up to the user which approach suits them, without the need to amend the OPTIONs panel, another CFG setting, etc., etc. Nevermind - I'll stick with my macro.
PS: Unsurprisingly, I have no demand for (FNFwd).
|
|
|
Post by George on Mar 28, 2021 13:52:29 GMT -5
Stefan: The problem is that RUN saves the file as a new .XXX file-type (matching the Editfile's extension). It has to save the file since it can't use the Edit filename (you might not want it over-ridden). THEN it lets Windows do whatever it likes based on the extension.
What filetype/extension does CLIP use? CLIP has no extension, so it is going to arbitrarily use .BAT for the temporary saved file.
Hmmm, maybe what we could do is to allow the 1st operand of RUN, if it starts with a period, to specify the desired extension. So if you have a REXX script in the CLIP session, you could say RUN .REXX (or RUN .CMD - whatever)
George
|
|
|
Post by Stefan on Mar 28, 2021 14:48:21 GMT -5
Robert, I gave up with Media Player a long while ago. If you want a capable and free alternative, try VLC from www.videolan.org/I don't know if it will fix the issue you described as I don't use FM in that way.
|
|
|
Post by George on Mar 29, 2021 10:39:28 GMT -5
Robert: See my other latest post. Not the same, but I altered FLISTS to support quoted or unquoted paths/filenames.
I'd prefer to just leave it to the user, they can simply enter CLIP and do a C ALL '"' '' to remove the quotes if needed.
George
|
|
|
Post by Stefan on Mar 29, 2021 12:16:40 GMT -5
WMP has some quirks where it seems to trigger 'external events' in SPFLite, for no good reason. I can play some song and then SPFLite's taskbar tab will blink, as if there was an open file that had an external file change. But when you go back to SPFLite, nothing has changed. It's like WMP creates a spurious file change event that's totally bogus. Very annoying.
Just a wild guess, but...
The Properties/Tag information stored within media files could potentially include something that Media Player updates when it plays the file.
I'm thinking of something like a 'Last-played' date/timestamp or 'Play-count'. If that were to happen, it might cause SPFLite to spot or be notified of the file change, especially if the file were open in an edit session. You'd have to ask George exactly under what circumstance the notification for 'file has been changed' occurs.
...as I said, just a thought as to why SPFLITE might "react" to the song being played.
|
|
|
Post by George on Mar 29, 2021 13:15:09 GMT -5
Robert: Stefan: One thing I've noticed with some Windows Apps (not sure if this is also WMP - don't use it) is that if you're not running full screen, and can still see some of the desktop, I've seen an obvious full desktop refresh be done. i.e. you can see desktop icons 'blink' quickly as they're re-drawn. I see this quite often after running an installer/uninstaller.
When that happens, all active windows are told to refresh/re-activate (whatever). If that happens, SPFLite will get the message and dutifully refresh/repaint everything. That's my theory of what you're seeing. Why WMP or other apps would do that I have no idea.
George
|
|
|
Post by mueh on Mar 30, 2021 3:28:36 GMT -5
George: Tested now 2.4.21088 Experienced following Problem . Sorted the Flist by full name . When RC * is done NAME* sort in FM doesn't display in Flist sequence . Seems to be 2.4 Problem since NAME* in 2.3 on a flist with this sequence and special characters works . Thanks for this feature . By the way i used similar approach by tayloring the flist with X line cmd's issued by macro depending on string's found/not found in Path/File name . Here the picture of the Problem You can see that last line in flist appears as 2'nd entry in FM display . This is't the rule . Take f.e a large Recent files list . Sort it and you should see differences in sequence in FM Name* display . Clicking on Path sort brings it in right sequence but should not Name* show it it in sequence of Flist ?
|
|
|
Post by George on Mar 30, 2021 9:41:45 GMT -5
MUEH: It seems the Name* sort was still building the sort key with the entry-type included as the first sort field. This is the field that says its a file, directory etc. And is how the Dir+, Dir- sort gets things in the right order.
For Name* it shouldn't be there, it should only sort on the physical sequence. I've removed it.
Thanks for spotting it.
George
|
|
|
Post by Jo on Mar 31, 2021 5:44:30 GMT -5
Sort on Lines seems not to work anymore. My column layout is NAME(36),LINES,LWDATETIME,SIZELONG
Jo
|
|
|
Post by Stefan on Mar 31, 2021 6:22:08 GMT -5
Hi guys,
Odd behaviour/potential bug observed with v2.4.21088
EDITSET just displays the OPTIONS dialog. Not what I expected.
The following only happened once - so may be a red herring. I cannot reproduce it.
FM: CUT with separate 'C' and 'CC..CC' commands builds the clipboard correctly, but a subsequent CLIP command shows pop-up: "The file name(s) in the UNDO control area do not appear to be valid The current UNDO SAVE function will be skipped"
No drama, just unexpected, especially given that I was on the FM screen, where, I assume, neither UNDO nor SAVE applies.
I did have an EDIT tab open with as yet unsaved changes, but still don't understand why 'UNDO SAVE' should be relevant.
Documentation change: File Manager Line Commands section - CLONE is now spelled KLONE.
|
|
|
Post by George on Mar 31, 2021 9:06:06 GMT -5
Jo: Good catch. The official field name "LINES" does not equal the column heading "Lines". Got to learn to use the correct variable name. Corrected.
George
|
|
|
Post by George on Mar 31, 2021 9:23:48 GMT -5
Stefan: EDITSET. Took a bit of digging, since I didn't even remember this variation (as well as EDSET).
Like you, I believed the description in the FM Primary commands.
However it's wrong. EDTISET/EDSET are actually aliases for OPTION. I call it dumb, but those aliases are direct from good old IBM ISPF-land. They're there for compatibility. But as an ISPF user for decades I'd never, ever used them (or even heard of them). They were added when we went on a campaign to ensure ISPF compatibility wherever possible.
We can just alter the FM doc. to correct it, but my actual preference is to just remove them. [UPDATE - That's what I'm going to do. [\UPDATE]
The UNDO thing - sounds like a bit of code normally only invoked for Edit sessions got invoked in the FM Tab. That message is new, I added it following Robert's problem with all the extraneous files being created and the suspicion they were UNDO related. Sure sounds like a track-down is needed. Thanks for reporting it.
George
George
|
|
|
Post by George on Mar 31, 2021 12:48:22 GMT -5
Another Beta release, this time with updated CHM and PDF files.
Also, the Change Edit Macro and Change Mapping support has been withdrawn.
See the 1st post in this thread for the download link.
George
|
|