DataMystic

Today, I installed TextPipe Standard (x32) v11.2

I then opened a filter I wrote yesterday and just clicked Save.

I observe afterwards that the saved filter file did not merely overwrite the old file,
but also saved it as a new file with "_NewFormat" inserted at the end of the filename before the extension ".fll"

After the file save operation, there was only one extra file in the MRU list, and that's without the "_NewFormat" suffix.

I was somewhat surprised at this feature change.

One consequence of this would be after the user updates any of the filters that were already part of his customized Windows Shell extension.

Unless the user also remembers to change the filename in the Windows Shell table, next time the filter was run from the Explorer Context Menu, it would still be the old format version that was run, which would probably be not what the user intended.

Likewise, for any filters run from a command line in a Windows CMD file.

Best regards,

David

A search of the Help Contents for "NewFormat" gave no results.

This seems to indicate that the filename suffix applied for the new JSON based filter files has not been documented.

Users need to be made much more aware of this change.

Or might it be the case that "_NewFormat" was merely a temporary change introduced during software development that has escaped into the released program?

If so, that's a cause for concern.

David

Further evidence.

If the user then opens the filter that had been saved with "_NewFormat" inserted automatically into the filename,
and then just clicks Save, this results in a third file that has a filename ending with "_NewFormat_NewFormat".fll

Even worse, the file that had just been opened (with only one "_NewFormat" suffix) was saved in the old binary format!!!

To say that this is confusing would be an understatement.

This leads me to be even more suspicious that the filename suffix "_NewFormat" was intended only during development for testing purposes.

David

Hi David, we've reverted back to v11.1 while we fix this snafu.

Wise move!

Fixed in v11.3
Improved in v11.4 to support UTF-8 in saved filter files.

Hurrah!