DataMystic

For a TextPipe filter that has a single input file and output file, it would be very useful to be able to Open Diff Tool upon completion.

i.e. To compare the input file with the output file.

At present, Open Diff Tool is hidden away under Extra options in the Trial Run Area.

Suggest add a tick box option next to Open output upon completion.

Regards,

David

Thanks, but as this only applies to the trial run area, I believe it should really remain where it is. Confusing otherwise.

I wouldn't be at all confusing, as long as the user was careful in how and when to automatically launch the external tool.

I have TextPipe configured to use WinMerge, but it seldom get's called, as I rarely use the TRA.

There are many time when I launch WinMerge after running a filter on a file, to double check while I'm debugging.

It's a vital part of a good Way of Working, especially if you're handling large files.
The TRA is more of a chore than a help when the data already exists externally.

Please reconsider.

David

Oh, external data. Ok, I'm with you. Good idea.

So would it compare each pair of input and output files?

And what if there were, say, 100 files? Would it only use the first 10?

Well there are all sorts of tangles a user could get into with this, to be sure.

He could have 15 secondary output filters too!
And he could have included restrict to each line in turn, which plays havoc with secondary output file updating!
Or she might be merging several input files into one processed output file.
More possible scenarios?

I'd be inclined to suggest the following:

Tickbox to enable/disable.
Counter to limit the number of times the Open Diff will attempt to open a new session of the Tool. Default = 1. Sensible upper limit.
NB. No action if the Tool has not been configured, or if the configured Tool has been uninstalled since.

Then if someone is processing 5 input files, each to a single output, they can decide whether to take the risk of having 5 WinMerge sessions open.

Anyone mad enough to expect his PC to remain stable with 100 such sessions, just "lay it on thick" in the context Help for the feature.
i.e. Plenty of warning of what might well happen.

David

Ok! I have a starting point now