L
Laura Stern
Guest
On your first point - yes, if you try to run a file that does not exist and you have a DO ON STOP anywhere above where that is called, it should "catch" it. STOP conditions bubble up until they are handled with DO ON STOP or you reach the top of the application. Re the WAIT-FOR issue, changing STOP to ERROR does not change the fact that you would still need to put CATCH blocks at least at the top of all UI triggers or event handlers. It will still not be particularly useful in the block containing the WAIT-FOR statement. Though there are times when .NET will throw an exception that will kick you out of Application:Run (i.e., the WAIT-FOR) and it would be nice to be able to CATCH it and show the error in a more friendly way. However, you would still not be able to RETRY that block. When .NET kicks you out of Application:Run like that, you cannot call it again. That has nothing to do with the AVM. It is a .NET "feature".
Continue reading...
Continue reading...