ImGearPresentationPageDisplay Class

An advanced version of the ImGearPageDisplay class that requires the Windows Presentation Framework and the ImageGear24.Presentation.dll assembly.

Object Model

Syntax

Visual Basic
C#
Managed Extensions for C++
C++/CLI

'Declaration
 
<TypeDescriptionProviderAttribute(MS.Internal.ComponentModel.DependencyObjectProvider)>
Public NotInheritable Class ImGearPresentationPageDisplay 
   Inherits System.Windows.DependencyObject
   Implements IImGearPageDisplay

'Usage
 
Dim instance As ImGearPresentationPageDisplay

[TypeDescriptionProvider(MS.Internal.ComponentModel.DependencyObjectProvider)]
public sealed class ImGearPresentationPageDisplay : System.Windows.DependencyObject, IImGearPageDisplay

[TypeDescriptionProvider(MS.Internal.ComponentModel.DependencyObjectProvider)]
public __gc __sealed class ImGearPresentationPageDisplay : public System.Windows.DependencyObject, IImGearPageDisplay

[TypeDescriptionProvider(MS.Internal.ComponentModel.DependencyObjectProvider)]
public ref class ImGearPresentationPageDisplay sealed : public System.Windows.DependencyObject, IImGearPageDisplay

Remarks

This class implements a set of display API for rendering an image specified by the Page property and annotations specified by the ARTPage property in the WPF environment. It is recommended that you use the ImGearPresentationPageDisplay class for WPF and FW 3.0 applications.

The ImGearPresentationPageDisplay class has been changed to derive from the System.Windows.DependencyObject class, allowing the Page, ARTPage, Channels, DICOMDisplaySettings, LUT, Orientation, Contrast, Brightness, and Gamma properties of this class to serve as the source or target of a binding.

Deriving from System.Windows.DependencyObject does create some new requirements that may affect applications upgrading to the new version. Because DependencyObject's have thread affinity, they should only be accessed from the thread on which they were created. Take the example where, using the previous version of ImageGear, an ImGearPresentationPageDisplay instance was created and stored within a ViewModel created in a background worker thread. After upgrading to the new version of ImageGear, the display object in the ViewModel will no longer be accessible from the thread where the application's main window is running.

To overcome this change, the data which the ImGearPresentationPageDisplay object uses as input should itself be stored within the ViewModel, instead of storing the display instance. Then, you can bind the properties of ImGearPresentationPageDisplay to the ViewModel.

Inheritance Hierarchy

System.Object
   System.Windows.Threading.DispatcherObject
      System.Windows.DependencyObject
         ImageGear.Display.ImGearPresentationPageDisplay

Reference

ImGearPresentationPageDisplay Members
ImageGear.Display Namespace