Loading in progress.

In this case, the progress is indicated by the two variables OIV.LDM.Nodes.SoLDMResourceParameters.FixedResolutionReport.numTilesToLoad and OIV.LDM.Nodes.SoLDMResourceParameters.FixedResolutionReport.numTilesLoaded. The current resources of the machine allow LDM to load the data at the specified resolution. In this case, the only possible way to receive an ABORT report code from the system is either if the user changes the resources (i.e., decreases the main memory space), or add some new geometry to the scene.

If LDM cannot grant a fixed resolution request, the delegatefunction is called with an ABORT report code.

In this case, LDM will automatically disable the fixed resolution mode. The FixedResolutionCB delegatewill be called with an ABORT report code in the following cases:

• The request to load the data at the specified resolution level (resolution argument in the enableFixedResolutionMode function) in main memory for the current geometry (either OIV.VolumeViz.Nodes.SoVolumeRender, OIV.VolumeViz.Nodes.SoVolumeSkin, OIV.VolumeViz.Nodes.SoOrthoSlice, OIV.VolumeViz.Nodes.SoObliqueSlice, volume geometries, or other LDM based render nodes) is not possible because the main memory space (set by the setMaxMainMemory function) is not large enough. In this case, the delegateis called with an ABORT code immediately after the first sceneGraph traversal, once the fixed resolution mode has been enabled.

• There was a geometry change (i.e., a geometry node was added to the scene graph) and there is not enough room in memory for the geometry nodes to be displayed at the current resolution level. In this case, the memory space needed in addition for LDM to be able to grant the request, is specified by the OIV.LDM.Nodes.SoLDMResourceParameters.FixedResolutionReport.numTilesToAdd variable. If there is enough main memory resources on the user machine, an automatic memory adjustment can then be realized by calling setMaxTilesInMainMem( getMaxTilesInMainMem() + numTilesToAdd ) right before enableFixedResolutionMode is called again. Those two calls can be done within the delegatefunction so LDM does not disable the fixed resolution mode after an ABORT report code has been sent.