First I never found anything in the errorText property also when the execute method return a non-zero value
Second ther are some condition that correctly return error in TextPipe but not in TextPipe Engine.
To check this I've exported some simple filter in vbscript, and changed the vb_generate_filter function in this way:
and then uncommented the last line to call the generate (and run) filter.
Code: Select all
sub vb_generate_filter() dim i vb_connectTextPipe vb_build_filter( vb_TPWindow ) i=vb_TPWindow.execute if i<>0 then MsgBox "ERROR " & i & vbCrLF & vb_TPWindow.errorText else MsgBox "OK" end if vb_disconnectTextPipe end sub 'End subroutine
I've try this using TextPipe (TP) end TextPipeEngine (TPE)
If the input file is missing TP show me an error message popup and then the script show an error without any message.
in the same test TPE give the vbscript error also without message.
if I build a wrong filter ( in example a Restrict lines without any subfilter ) the TP show a popup an then return error (again without anything in the errorText property)
but TPE return OK!!
It will be very difficult to work without the capability to correctly report the errors to the user.
Is there any workaround for this issue ?