Filters started by Windows shell don't output any file

[dfhtextpipe]

Something is now seriously amiss with how TextPipe works in the Windows Shell.

All my well-established filters that I use from Windows shell extensions have stopped outputting any file.

Everything was working fine until TextPipe Standard 8.4.3 (and I conformed this today, by reverting successively to earlier versions).

The most recent three updates (8.4.4 / 8.4.5 / 8.4.6) do not produce an output file!

When they were working before, they would write the output file in the same directory.

These well-established filters still work when a file is specified to be processed and TextPipe 8.4.6 is started by the Go command from within the application.
This is evidence that there is nothing amiss with the actual filters.

[DataMystic Support]

Are you running these filters on actual files (remember that these newer versions remove existing files from the file list before adding those files that the shell extension is triggered for).

[dfhtextpipe]

Simon,

There has definitely been a change in the way the shell extension works.

I just use the Windows context menu, and select a suitable filter to apply to the file selected in Windows Explorer.
There is a momentary appearance of TextPipe, but it closes before I can read what's happening.
That's because all my old shell extensions had the /q switch to close on completion.

The filters themselves do not specify any files, so I do not specify /clearfiles in the shell command.

David

[DataMystic Support]

/fromshellext is specified automatically when a filter is run from the shell extension. There was a bug in the way this was being added, this will be fixed in 8.4.8 later today

[dfhtextpipe]

Simon,

Thanks for checking this out. I eagerly await the solution.

Best regards,
David Haslam

[dfhtextpipe]

TextPipe Standard 8.4.8 is now installed.

It has solved this issue. Thanks.

David

[DataMystic Support]

Great - thanks for confirming the fix.