Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Terminating an application which runs in the background Date: Tue, 28 Mar 2017 09:54:42 +0200 Lines: 32 Message-ID: References: <0c459c45-4199-4fd7-acac-e6c5f2e66b58@googlegroups.com> <5a9a7f2c-3cf1-460a-aa98-7d1715b056bd@googlegroups.com> <7d5647d5-00c2-4061-b082-5a6b1364bace@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: individual.net 0ZPl0/i1BF0oegIsrSUKsg1n911DZTtjAGjz+J7Y2O0aVt/ts= Cancel-Lock: sha1:iqozpMRryKE/MZSghrqiEHYvC40= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:10356 Hi Stefan, > > of course this is possible - and I do it all the time. Just install > > your own error handler and it will be called when an error occurs. > > In this error handler, depending on the situation, you could > > terminate the child process. > > But then you must overwrite the DefError function, loosing its > handling, right? yes. But you have two possibilities: - copy the DefError code to your own error handler and enhance it. - keep a copy of the DefError handler somewhere and chain it > At all, the DefError function does not stand for object oriented > programming. The handling of DefError should be in a class, from > which a developer could derive its own class. please don't forget that the DefError concept is more than 20 years old, and was taken over from Clipper. But if you like, of course you can rewrite the complete error system of Visual Objects - instead of a codeblock you can also use an object with an Eval() method (unfortunately this fact is not widely known, but permits also detached locals as part of this object). Wolfgang --