in reply to Error Handling

You say that identify crashes, but it generates a window... is it still running or not? I suppose it is running, since I would find strange that it spawns another process just to tell you it is crashing. So, with this in mind...

Instead of using system you could fork a child process that launches identify, and use alarm in the parent.

If the child process doesn't return in a fixed amount of seconds (as far as I can understand, 10 is far more than enough), its parent could kill it and go on with next image.

Have you any experience on that?

Replies are listed 'Best First'.
Re: Re: Error Handling
by sdyates (Scribe) on Jun 24, 2002 at 16:00 UTC

    Well, this is windows which makes things a little different. The identify will go away but requires the clicking of an ok or cancel button. I need to redirect the program error so that window's dialogue does not appear waiting for an ok or cancel button to appear.

    This would be much easier if it was run in linux. Windows always has to make things difficult!