|
Handling non-fatal VRML files errors.
When our VRML engine encounters a problem with VRML file, it tries to report it, but also to continue work if possible. This way many incorrect VRML files are reported but we still handle them. In fact, VRML requires that some resource problems (missing URL resource, like a texture or inline or external prototype that can't be accessed) are handled gracefully.
All such cases with problematic VRML content are reported to VRMLNonFatalError. You can assign any procedure to VRMLNonFatalError.
You can report the problem and continue. This is suggested for general VRML browsers like view3dscene, that must handle any VRML content gracefully. E.g. use VRMLNonFatalError_WarningWrite. You can raise an exception, that will possibly stop your program. This may be appropriate for cases when you have some control over VRML content, and you do not want to tolerate problems with VRML data. E.g. it may be appropriate for games with VRML data. See VRMLNonFatalError_RaiseEVRMLError for this. You can even simply ignore the problem by VRMLNonFatalError_Ignore (this procedure simply does nothing).
|