DataMystic

Posted: **Fri Nov 20, 2009 11:46 pm**

I've found some issue in error handling:
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:

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

and then uncommented the last line to call the generate (and run) filter.

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 ?

Thanks.

Posted: **Fri Nov 27, 2009 1:07 pm**

Hi there,

We've just released a beta for you - 8.4.7
- Modified TextPipe and TextPipe Engine so that error messages are now available through the ErrorText variable when called via COM.

The TextPipe Beta (in the secure area) has been updated, and so has TextPipe Engine, but the main releases will not get updated for a few days.

Please give them a try and see how they go. Let us know if any further changes are required.

Posted: **Mon Nov 30, 2009 10:41 pm**

just downloaded it.
I will post some feedback soon.

thank.

Posted: **Tue Dec 01, 2009 1:52 am**

I've found this issue with a restrict without subfilter
( I know is a wrong filter, but my app is building it dynamically)

Code: Select all

Filter options
|  [ ] Log to file
|  [ ] Append to logfile
|  Log filename: 
|  Threshold 0
|
|--Input from file(s)
|     [ ] Confirm before processing each file
|     [ ] Confirm before processing read/only files
|     [ ] Delete input files after processing
|     Process binary files
|   
|--Restrict to filenames NOT matching perl pattern [^1(.*)$]
|   
+--Output to file(s)
      [ ] Only update date on changed files
      [ ] Append mode
      [ ] Change extension to: 
      [ ] Open output file
    Test mode      [ ] Remove empty output files

when run from UI it give an "Access Violation" error.
when run from COM Automation it return OK.

Posted: **Thu Dec 03, 2009 12:17 pm**

Thanks - will be fixed in 8.4.8 later today

DataMystic

Error Handling in TP Engine

Error Handling in TP Engine

Re: Error Handling in TP Engine

Re: Error Handling in TP Engine

Re: Error Handling in TP Engine

Re: Error Handling in TP Engine