No thats called: professional error handling
Or do you believe that all the nice error messages you see in other apps are C++ error messages?
Try - Catch - EndTry is the only way to get a usefull error handling.
BM can not know that you killed a graphics command because the error won't be raised until function xy tries to access the _graphics:TGraphics which is null and that basically can be about anything. graphic command but potentially anything else you added to the module like SetCanvasGraphics etc.
Giving BM the possibility to find the source of the error means that it is slower during the times it does not error ...
Quite a great thing just to satisfy users that don't get the basics of common error handling practices.
If you are too lazy for it, invest in Grey Aliens Framework. It will handle this kind of stuff for you without any extra work for you.
Or do you believe that all the nice error messages you see in other apps are C++ error messages?
Try - Catch - EndTry is the only way to get a usefull error handling.
BM can not know that you killed a graphics command because the error won't be raised until function xy tries to access the _graphics:TGraphics which is null and that basically can be about anything. graphic command but potentially anything else you added to the module like SetCanvasGraphics etc.
Giving BM the possibility to find the source of the error means that it is slower during the times it does not error ...
Quite a great thing just to satisfy users that don't get the basics of common error handling practices.
If you are too lazy for it, invest in Grey Aliens Framework. It will handle this kind of stuff for you without any extra work for you.