andy
Freshman Member
Posts: 17
|
Post by andy on Jan 27, 2023 5:41:23 GMT -5
Hi
Is there any way to 'diff' two clips without copying them to files first?
I have tried 'diff 2 3' but it brings up the DIFF options panel and then tells me that 'FileA cannot be null or blank'.
Thanks
Andy
|
|
|
Post by Robert on Jan 27, 2023 9:15:28 GMT -5
Andy, based on what I know (though not a DIFF expert), I don't think you can do what you had in mind.
If you are in the habit of needing this frequently, you could set up two 'work files' that you continually reuse, like C:\TEMP\WORK1.TXT and C:TEMP\WORK2.TXT and then compare those files.
To make this more convenient to type as a command, you could define SET symbols, like this:
SET WORK1 = "C:\TEMP\WORK1.TXT" SET WORK2 = "C:\TEMP\WORK2.TXT"
Then when you need to do your DIFF, you'd save each clip edit session like: CREATE =WORK1 CREATE =WORK2
Then you'd have these common work files available.
Not the most convenient way, but I can't think of how else this could be done, without DIFF being modified somehow. It would be a tricky change to make, because there is no way for one edit session to "reach over" to another edit tab and grab its data. SPFLite doesn't work that way. If you have existing, saved files, that's one thing. But to access one CLIP session from another CLIP session? Technically, I don't believe it's possible for SPFLite to work that way.
Maybe a DIFF expert out there can jump in and offer some help.
|
|
andy
Freshman Member
Posts: 17
|
Post by andy on Jan 27, 2023 10:08:10 GMT -5
Hi R
What led me down the path of wishful thinking was this statement in the Features section of the DIFF Compare help page - first feature...
If the files being compared are already loaded into SPFLite tabs, then the entire operation is performed with no external I/O and is extremely fast.
So, my logic goes, the clips are in tabs, I have specified the tab numbers, go compare...
Andy
|
|
|
Post by Robert on Jan 27, 2023 10:33:38 GMT -5
post deleted
|
|
|
Post by George on Jan 27, 2023 12:44:04 GMT -5
Andy: Robert: Pretty dumb oversight on my part. I've corrected it, will be available in the next Beta.
George
|
|
|
Post by Stefan on Feb 11, 2023 9:01:58 GMT -5
George,
If users issue the DIFF command against one or two CLIP sessions, these sessions are obviously not associated with a file profile and thus some DIFF options are not available as they need data from an AUTO file.
Could this be overcome by adding a field to the DIFF dialog where a user could specifiy a Profile/AUTO file to use during comparison?
Assuming folks compare files of a similar nature, you'd only need one field, not one each for FileA and FileB.
Indeed, if the comparison is between a real file and a CLIP session, you could assume both are of the same file type and apply the real file's AUTO information to both tabs.
|
|
|
Post by George on Feb 11, 2023 9:42:11 GMT -5
Stefan: Well, the DIFF dialog is already pretty loaded. If you're thinking of the comment removal, be aware that DIFFs removal is abbreviated compared to colorization, enhancing that is another whole problem.
George
|
|
|
Post by Stefan on Feb 11, 2023 10:00:07 GMT -5
No drama if it's a pain. I was comparing bits of a program with Clip data of the same file type and wouldn't even have noticed this if the "Ignore Comments" setting hadn't been "remembered" from a previous comparison.
That's when it occured to me that there may well be a suitable AUTO file for the CLIP data, but there's no way to tell Spflite about it. Or, it could default to using the same AUTO file as the other participant, if available.
|
|
|
Post by George on Feb 11, 2023 12:26:50 GMT -5
Stefan: The DIFF routine is convoluted as it has to cope with comparing two loaded file tabs, two CLIP sessions, a mixture of the two or even two other files that aren't even loaded. So it may or may not have to open new tabs and load data. Getting that done and passing possible overriding Profiles may just get to be too much.
George
|
|