For Microsoft Windows users seeking Kodak Imaging for Windows capabilities and for developers who have used the ActiveX (OCX) controls to integrate imaging functionality within applications, Global360 Imaging for Windows provides the Imaging features found in Microsoft Windows 95 through to Windows 2000 but no longer included in Windows XP, Windows Vista or Windows 7, 8 or 10.
The ActiveX controls ImgEdit, ImgAdmin, ImgThumb, ImgScan and ImgOCR are included. Release 4.0 adds an ImgPdf control.
A Software Development Kit is available to enable the ActiveX controls. The SDK is known as the Imaging for Windows 4.0 Developer Resources Kit.
Imaging for Windows Developer Resources is a separately packaged and licensed offering that enables organisations to leverage powerful, highly-developed ActiveX controls to create robust custom applications with integrated imaging capabilities.
The Imaging for Windows ActiveX controls enable software developers to add imaging capabilities to custom applications and programs that support ActiveX, including for Visual Basic (VB6) and Visual C++ programming.
The "Imaging for Windows 4.0 Developer Resources Kit" can either enable the ActiveX controls supplied with the "Imaging for Windows 4.0" end-user application, or can enable the ActiveX controls only product "Imaging for Windows 4.0 Developer Resources licence pack". In either case, one licence per PC is required.
The following controls are included with Imaging for Windows Developer Resources:
- Image Edit Control (imgedit. ocx) – Displays, annotates, manipulates, and manages image files.
- Image Annotation Tool Button Control (included with imgedit.ocx) – Adds text and graphical annotations to displayed image files.
- Image Scan Control (imgscan.ocx) – Scans paper documents via TWAIN-compatible scanners.
- Image Thumbnail Control (imgthumb.ocx) – Displays thumbnail views of images contained in an image file.
- Image OCR Control (imgocr.ocx) – Converts image files to formatted, editable text.
- Image Administration Control (imgadmin.ocx) – Administers image files, provides common dialog boxes for image operations, and manipulates pages within an image file.
- Image PDF Control (imgpdf.ocx) – A new Imaging for Windows 4.0 control adds PDF display and print functions to applications.
Technical Requirements
- Intel Pentium or equivalent processor.
- Windows 10, Windows 8, Windows 7, Windows Vista™ with Service Pack 1 (or later), or Windows XP with Service Pack 2 (or later).
- 64 MB RAM or more for Windows 2000 and Windows XP, or 1 GB RAM or more for Windows Vista or later.
- At least 35 MB of available hard disk space on the system drive.
- VGA controller with at least 1 MB of memory.
- TWAIN-compliant scanner or other device (optional) and fax/modem card (optional) to take advantage of Global 360 Imaging for Windows scanning and faxing capabilities.
- A programming language or application capable of supporting ActiveX or OCX. VB6 (Visual Basic) and Excel are suitable.
Licencing Requirements
- Windows 2000, Windows NT and Windows 98 include a free, non-distributable, version of Imaging for Windows without the OCR(Optical Character Recognition) and other advanced features of Global 360 Imaging for Windows.
- Windows XP and later does not include a free version of Imaging for Windows, and free versions from older operating systems may not be installed upon it.
- Global 360 Imaging for Windows requires one licence for each PC it is installed on. Volume licence packs are available.
- For Windows XP, Vista and Windows 7, 8 and 10, a Software Development Kit ("Developer Resources Kit") is required. SDKs are available for in-house application development or for developing applications for resale.
- The ActiveX controls in Imaging for Windows 4.0 are not enabled until you obtain a Developer Resources Kit.
Developer Resources package
- The Developer Resources package includes ActiveX Controls (OCX), OCX Online Help, Developer’s Guide, and Samples
- Developer Resources may be used for software development. Each PC requires a a license, which may be either an end-user Imaging for Windows 4 licence (which provides an end-user application as well as allowing software development) or a developer licence
Using with Imaging for Windows 4.0 End-User licenses
- The end-user Imaging for Windows 4.0 application includes the ActiveXs, but they are not enabled until you have a Developer Resources Kit license.
- IMAGING4.0-DEV Developer Resources Kit enables the ActiveXs included with the end-user Imaging for Windows application, allowing software development. You must have one end-user Imaging for Windows 4.0 license (IMAGING4.0-LP-x) for each PC. Note the IMAGING4.0-DEV Developer Resources Kit is for development purposes only and may not be used in live systems.
Using without Imaging for Windows 4.0 End-User licenses
- The Imaging for Windows 4.0 ActiveXs are available without the end-user application. A Developer Resources Kit license is also required.
- IMAGING4.0-DEV Developer Resources Kit enables the use of the Imaging for Windows 4.0 ActiveX licences purchased as a License Pack (IMAGING4.0-DEV-LP-VOL, see below, minimum order quantity 30 licenses per order). Note the IMAGING4.0-DEV Developer Resources Kit is for development purposes only and may not be used in live systems.
- IMAGING4.0-DEV-LP-VOL is the individual license pack, providing the right to use the ActiveX controls (but not the end-user Imaging for Windows 4.0 application). One license is required per PC, minimum order quantity 30 licences.
License Check - A LicenseCheck() instruction is required in any application using the Imaging 4.0 ActiveX controls. For the trial period the LicenseCheck() method must still be called but a null can be use instead of the file - LicenseCheck(“”)
Example:
Each OCX control has a LicenseCheck method. You need only use the method once in an application (not for each OCX). Typically this will be near the start of the application.
ImgAdmin.LicenseCheck(LicensePath) where 'LicensePath' is the full filepath and name of the developer licence file.
or
ImgEdit.LicenseCheck(LicensePath)
This method returns 0 if the Licence is invalid or -1 for a valid licence code file
The developer licence is the file with a .lic extension eg "Imaging_12345678-a123-b123-c123-d123-1234a567b8c9.lic"
This file may, for example, be placed in C:\Program Files (x86)\Common Files\Global360\Imaging
During the evaluation trial period this check must still be done in your source code, but a null can be used for the license path ImgAdmin.LicenseCheck("")
