Hi Fons,
this is what I am doing:
Abort("Bad stream to file. Trying next image.", kAbortFile);
However the code always continues at the next event in my cases. Can you point me where the TSelector::GetAbort() is done, I only see it catching kAbortProcess, not kAbortFile
Constantin
On 04/07/2011 04:08 PM, Fons Rademakers wrote:
> Hi Constantin,
>
> you should call in you TMySelector:
>
> Abort("corrupted data", kAbortFile);
>
> in case you have some problem with the data in the current file. Then the the processor that calls the selector, will load a new files and continue processing. In more severe cases you can call:
>
> Abort("processing screwed up, aborting", kAbortProcess);
>
> and in this case the processing will abort.
>
> the chain/tree/proof processor uses the TSelector::GetAbort() method to decide what to do.
>
> Hope this is clear.
>
> Cheers, Fons.
>
>
> On 07/04/2011 14:35, Constantin Loizides wrote:
>> Dear all,
>> in TSelector there is an Abort function that is advertised to be used
>> to Abort the current file and move to the next file of the Chain.
>> However it does not seem to do anything. Grepping v5.28.00b
>> for TSelector::kAbortFile does not return any hit.
>> Is this feature not implemented? Or am I overlooking something?
>> Thanks Constantin
>>
>
Received on Thu Apr 07 2011 - 17:01:29 CEST
This archive was generated by hypermail 2.2.0 : Thu Apr 07 2011 - 17:50:01 CEST