The following table outlines the major differences between the ImageKit.NET3 and the earlier version, ImageKit.NET2. Please refer to this table when using older ImageKit.NET2 code with the ImageKit.NET3
In most cases, older ImageKit.NET2 code will run without errors. However, there are property and method name changes or parameter changes that might cause errors.
Name | Explanation of Change |
---|---|
ImageKit.Win.ImageKit | |
Eliminated Items | |
Properties: | |
Refine1BitImage, RefineColorImage |
These properties set whether an image, when reduced in size, is displayed in high quality display. They have been discontinued. *1 |
ToolBar | The ImageKit.NET2 Toolbar control has been replaced by four new toolbar controls: ToolBarStandard, ToolBarAnnotation, ToolBarSetupLines, and ToolBarSetupObjects. These new toolbars allow many ImageKit control related functions to be set by toolbars only. The old ToolBar property has been deprecated but is maintained for backwards compatiblity. Please use the above 4 toolbar controls instead. |
Changed Items | |
Methods: | |
Display | The DisplayMode property has been added to replace the display mode parameter in the old Display method. This new Display method takes no parameters. *2 |
ImageKit.Win.ImageKit.Edit | |
Eliminated Items | |
Properties: | |
EnableTextDialog | This property has been eliminated. Instead of a single property dialog used for all annotation objects, selected objects will display their own property dialog depending on the type of annotation object. |
TextDialog***Visible, TextDialog***Enabled |
These two properties were text object specific and have been eliminated. Instead, each item in an object's property dialog can be displayed or hidden (the Dialog****Visable properties), enabled or disabled (the Dialog***Enabled properties). |
Methods: | |
DeleteMultiSelectedObjects | This method has been combined with the DeleteSelectedObject method. It no longer matters whether or not an object was selected as a single object or selected as one of multiple objects. The DeleteSelectedObject method will delete them. |
SetSelectedObject*** | It is now possible to set properties directly using the SelectedObject*** properties so this method is no longer needed. |
Changed Items | |
Properties: | |
EditEnable | The name has been changed to EditEnabled. The old EditEnable property is maintained for reverse compatibility and will not result in an error. Use the new EditEnabled property instead. |
SelectedObject*** | SelectedObject*** properties are no longer readonly. They can now be set. |
SelectedObjectDrawPoints | Important!! This property type has been
changed from List<Point> to Point[]. This means that old code MUST be changed to reflect the new type! |
Methods: | |
LoadImageFromFile | All LoadTypes are automatically detected so this method has no parameters. *3 |
LoadImageFromRawData | All LoadTypes are automatically detected so this method has no parameters. *3 |
ImageKit.Win.ImageKit.Effect | |
Changed Items | |
Methods: | |
Chroma | The name of this method has been changed to SetChroma *2 |
RedEyeRemoval | The name of this method has been changed to RemoveRedEye *2 |
Rotation | The name of this method has been changed to Rotate *2 |
Sharp | The name of this method has been changed to Sharpen *2 |
ImageKit.Win.ImageKit.File | |
Eliminated Items | |
Properties: | |
TiffAppend | This property is no longer needed. Use the following new methods for processing multi-page tiff images instead: AppendTiffImage, InsertPageIntoMultipageTiff, and DeletePageFromMultipageTiff. |
Methods: | |
CloseMultiTiff | This method is no longer needed. Use the following new methods for processing multi-page tiff images instead: AppendTiffImage, InsertPageIntoMultipageTiff, and DeletePageFromMultipageTiff. |
*1: Function will not cause an error but will be ignored
*2: The older property or method is maintained for backward
compatibility. It will execute and not generate and error however
we recommend that you use the newer property or method.
*3: The old method remains to maintain backwards compatibility but
regardless of the parameter used, the LoadType will automatically
be detected. Use the newer form of the method going forward.