LDicomDS::SetImageList

#include "Ltdic.h"

L_UINT16 LDicomDS::SetImageList(pElement, hList, nCompression, nPhotometric, nBitsPerPixel, nQFactor, uFlags)

Replaces the images in a Pixel Data element with images in an image list.

Parameters

pDICOMELEMENT pElement

Pointer to a DICOMELEMENT structure within the Data Set.

HBITMAPLIST hList

Handle to the list of images.

L_INT32 nCompression

Value that indicates the type of compression to use, which are affect the way the image is compressed when call the function. Possible values are:

L_INT32 nPhotometric

Photometric constant. Possible values are:

L_INT32 nBitsPerPixel

Resulting image pixel depth. The following are valid values:

L_INT32 nQFactor

The quality factor (Q factor) is a number that determines the degree of loss in the compression process. You can set a value from 2 to 255, where 2 is the highest quality and 255 is the most compression.

L_UINT uFlags

Flags which control the behaviour of this function. Possible values are:

Returns

Comments

This function replaces all the images in the Pixel Data Element with the images referenced by hList.

Most DICOM files will only have one Data Element of type TAG_PIXEL_DATA. Therefore, in most instances you can set pElement to NULL, since the function will automatically replace the images of the only Pixel Data Element in the file. If pElement is not NULL, it must point to the Pixel Data Element itself.

If the DICOM file is CLASS_BASIC_DIRECTORY, the file may contain more than one Pixel Data Element. In this case you must specify in pElement the Pixel Data Element in which the images will be replaced.

If you wish to replace only one image within the Pixel Data Element, you must use LDicomDS::DeleteImage and LDicomDS::InsertImage.

For a table of possible Compression, Photometric, BitsPerPixel, and Quality Factor combinations, refer to Compression Table.

For more options when using the JPEG 2000 compression, refer to LDicomDS::SetJ2KOptions.

This function will either insert, delete or update one or more of the following elements:

If the Shared Functional Groups Sequence element or the Per-frame Functional Groups Sequence element is added, an item child element may be added that contains either the (0028,9132) Frame VOI LUT Sequence element or the (0028,9145) Pixel Value Transformation Sequence element.

(0028,9132) Frame VOI LUT Sequence Child Elements

(0028,9145) Pixel Value Transformation Sequence child elements

This function is indifferent to the pixel data restrictions imposed by the various DICOM IOD classes, for example this function will allow the user to insert a colored image into a "Digital X-Ray Image Storage" dataset.

This function will always insert a "Number of Frames" (0028, 0008) element and set its value.

The Multi-frame Functional Groups module may have a Shared Functional Groups Sequence item, and/or a Per-frame Functional Groups Sequence item. Either of these items may have a Pixel Value Transformation Sequence (0028,9145) item, or a Frame VOI LUT Sequence (0028,9132) item.

When calling the functions LDicomDS::SetImage or [LDicomDS:SetImageList, the five DICOM_SETIMAGE_MFG replace existing information in the Pixel Value Transformation Sequence or the Frame VOI LUT Sequence, and  any existing Shared Functional Groups Sequence items, and Per-frame Functional Groups Sequence items will be removed.

• DICOM_SETIMAGE_MFG_VOI_LUT_PER_FRAME
• DICOM_SETIMAGE_MFG_VOI_LUT_SHARED
• DICOM_SETIMAGE_MFG_MODALITY_LUT_PER_FRAME
• DICOM_SETIMAGE_MFG_MODALITY_LUT_SHARED

Any new sequences are placed in the sequence indicated by the flag (Per-frame Functional Groups Sequence or Shared Functional Groups Sequence).

For a detailed discussion on Multi-frame Functional Groups and how the DICOM_SET_IMAGE_MFG flags are used, see the topic Multi-frame Functional Groups.

NOTE:

DICOM_SETIMAGE_MFG_VOI_LUT_PER_FRAME cannot be combined with DICOM_SETIMAGE_MFG_VOI_LUT_SHARED.

DICOM_SETIMAGE_MFG_MODALITY_LUT_PER_FRAME cannot be combined with DICOM_SETIMAGE_MFG_MODALITY_LUT_SHARED.

Note that the only valid values are for nPhotometric are:

• IMAGE_PHOTOMETRIC_MONOCHROME2 (gray)

• IMAGE_PHOTOMETRIC_PALETTE_COLOR (palletized)

• IMAGE_PHOTOMETRIC_RGB (Color)

All other values are ignored.

The nPhotometric  parameter is used as an indicator as how the data image data will be saved: gray, color, or palletized. The nPhotometric parameter is NOT necessarily going to be the final value of the Photometric Interpretation that is stored in the resulting DICOM dataset.  The resulting Photometric Interpretation in the DICOM dataset is set automatically, based on the compression type, flags, and QFactor.  The table below gives examples of the resulting DICOM dataset Photometric Interpretation, based on various input parameters:

NOTES:

• There is no high level function to embed MPEG2 into a DICOM dataset. The Multimedia toolkit (DICOM writer) can create DICOM files with MPEG2 compression.

• This function cannot be used to encode DICOM transfer syntaxes (e.g. video compression support) that are not part of the main medical SDK and it is supported only via the LEADTOOLS Medical Multimedia Module.

Required DLLs and Libraries

• LTDIC
• For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application

Platforms

Win32, x64

L_INT LDicomDS_SetImageListExample(HBITMAPLIST hList) 
{ 
   L_INT          nRet; 
   LDicomDS      *pDS; 
   pDICOMELEMENT  pElement; 
 
   pDS = new LDicomDS(NULL); 
 
   nRet = pDS->LoadDS(MAKE_IMAGE_PATH(TEXT("image1.dcm")), 0); 
   if(nRet != DICOM_SUCCESS) 
      return nRet; 
 
   pElement = pDS->FindFirstElement(NULL, TAG_PIXEL_DATA, FALSE); 
   if (pElement != NULL) 
   { 
      nRet = pDS->SetImageList(pElement, hList, IMAGE_COMPRESSION_JPEG_LOSSLESS, 
                        IMAGE_PHOTOMETRIC_RGB, 0, 0, DICOM_SETIMAGE_AUTO_SET_VOI_LUT); 
      if(nRet != DICOM_SUCCESS) 
         return nRet; 
   } 
 
   delete pDS; 
 
   return DICOM_SUCCESS; 
}