DataMystic

If I insert the sample script filter in special filters and change it from VBScript to JScript, when I do a trial run, I get the following error message, even though logging is not enabled.

https://www.dropbox.com/s/umquiosqxsiah ... 0.png?dl=0

This was with TextPipe v9.9.5

Best regards,

David

In TextPipe v10.0 - once I'd selected JScript, it became impossible subsequently to use a VBscript filter.

The error message for JScript is this:

https://www.dropbox.com/s/hy1ivvyzagvim ... 7.png?dl=0

Once the above error message has been generated, even if you reselect VBScript, you cannot get any other response except this.

That's still the case even after closing TextPipe and relaunching it. Perhaps something gets set permanently in the registry?

Best regards,

David

Having still both TextPipe Pro v9.9.5 BETA (32-bit) and TextPipe Standard x64 v10.0 installed, I subsequently observed that after the above JScript error message had been generated by TextPipe v10.0, I could no longer even insert the sample VBscript filter in TextPipe v9.9.5

Looks like I was right about the registry!

David

I just examined the registry entries for TextPipe in HKCU Software DataMystic TextPipe

This may be the location that affects such behaviour: I tried editing this key to change the value to "VBScript" to see if the sample filter can be added again.
This was successful with TextPipe v9.9.5 and then with v10.0 - though only the former allows the sample VBScript to run.

Regards,

David

The preferred solution to this issue would be to provide a separate sample script filter for JScript.

NB. This might require a change in the UI.

David

Hi David,

You can set your own sample JScript filter, by pasting text in, and choosing the [Set Default] button.

I did not see the same behaviour as you with the steps described. I have the http://www.datamystic.com/tsc64_1000.cab x64 activex script control installed.