DicomObjects.NET8 Documentation
DicomObjects Namespace / DicomAssociation Class / ChangeLossyUIDs Property



In This Topic
    ChangeLossyUIDs Property (DicomAssociation)
    In This Topic
    Control allocation of new UIDs for lossy compressed images
    Syntax
    'Declaration
     
    
    <ObsoleteAttribute("This property has been superceded by WriteBehaviours.ChangeLossyUIDs, which is more flexible, including use when writing files")>
    Public Property ChangeLossyUIDs As Boolean
    'Usage
     
    
    Dim instance As DicomAssociation
    Dim value As Boolean
     
    instance.ChangeLossyUIDs = value
     
    value = instance.ChangeLossyUIDs
    [Obsolete("This property has been superceded by WriteBehaviours.ChangeLossyUIDs, which is more flexible, including use when writing files")]
    public bool ChangeLossyUIDs {get; set;}
    [Obsolete("This property has been superceded by WriteBehaviours.ChangeLossyUIDs, which is more flexible, including use when writing files")]
    public:
    property bool ChangeLossyUIDs {
       bool get();
       void set (    bool value);
    }
    Remarks
    There are times when the negotiated transfer syntaxes for a DicomConnection require a previously uncompressed (or losslessly compressed) image to be transmmited in a lossy form. Although the DICOM standard is not entirely clear, most people believe that a new instance UID should be generated whenever this happens. This is the normal DicomObjects behaviour, and a reference to the original UID is included in the referenced image sequence. However, some query SCUs having requested a specific image by it's UID fail to look in the referenced image sequence and reject images with UIDs other than those they had requested. The default value of this property is copied from DicomGlobal.ChangeLossyUIDs (which itself has a default value of true), but if set to false, then images sent via SendInstances which undergo lossy compression will not have new UIDs allocated.
    Requirements

    Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

    See Also