The primary purpose of this control is the display of DICOM images, and extensive facilities are available to allow images to be obtained from a variety of sources, including files and network operations. There is extensive control over how the images are displayed, including not only the normal width/level controls, but also use of DICOM greyscale presentation states, a wide range of annotations, flipping, zooming etc.
Images received via C-STORE operations are, by default, stored in memory and displayed. Any number of images can be received (subject to memory limitations), and may be displayed either singly or in combination. Images may be "windowed", and their various attributes, (including the pixel data), are available to the container application. Images may be selectively deleted, duplicated or re-ordered. They may also be stored and retrieved to/from files or database fields.
A major design feature is that this control has no intrinsic user interface other than the display itself, all functionality being exposed and implemented via OLE automation interfaces. In general, as much functionality as possible is devolved to the container. For instance, the control does not have its own application entity name, and acceptance or rejection of associations is controlled via an event. This event is given the remote IP address and the calling and called application entity titles, allowing the container to make its own accept/reject decision.
Similarly, other SCP functionality is expressed entirely through events, allowing the control to respond as required by the container.