| synopsis || return value || arguments || prev |
virtual kdu_roi_node * acquire_node( int component, kdu_dims tile_region)
Java: Kdu_roi_node Acquire_node( int component, Kdu_dims tile_region)
[Declared in "../coresys/common/kdu_roi_processing.h"]
Acquires a suitably derived kdu_roi_node object, which is capable of delivering the ROI information for the indicated image component, confined to the indicated tile region.
May return NULL if the entire region or component is to be interpreted as part of the foreground. Otherwise, the returned kdu_roi_node object should be released (through kdu_roi_node::release) once the application is done with it. Usually, the node will be supplied in the constructor for a sample data processing engine (see kdu_analysis::kdu_analysis or kdu_encoder::kdu_encoder), in which case the relevant object will take care of these release responsibilities itself.
Image components start from 0.
Regions supplied here are expected to form a partition of the image region, mapped to the relevant image component. Specifically, the tile_region will normally be that returned by the kdu_resolution::get_dims function, applied to the highest resolution of the relevant tile-component (that recovered using kdu_tile_comp::access_resolution). The reason for supplying explicit tile region coordinates rather than tile indices is to relieve the implementation of the derived kdu_image object from having to understand tiles. The partition requirement ensures that every requested region will belong to the region occupied by the relevant image component and that no two requested regions will overlap.
| top || synopsis || return value || arguments || prev |