| HotFixes for Imaging for Windows 2.8 |
| |
| |
| HotFix 50 completely replaces and supercedes all preceding Imaging
2.8 HotFixes.
If a newer version of Internet Explorer is installed after Imaging for
Windows, or after an Imaging for Windows Hotfix, there may be a problem
running the ActiveX controls in HTML or with Microsoft Office. To resolve
this problem, either merge the registry file, activex compatibility -
restore.reg (included in this Hotfix package), into the system registry by
double-clicking on the file or re-install this HotFix.
Issues Resolved:
HotFix 50:
Due to potential backward compatibility problems, the ClearDisplay() extension
added to HotFix48 has been modified: Instead of the optional "ClearCacheFile"
argument added to ClearDisplay(), a new method, ClearDisplayEx(), has been added
to include the optional argument, and ClearDisplay() has been restored to its
original (no-argument) syntax. Customers requiring the new "ClearCacheFile"
option should change their calls to use the new ClearDisplayEx() method instead.
HotFix 49:
This hotfix corrects several internal memory leaks that may be contributing to
problems encountered with a customer application doing repeated ImgEdit
ClipboardCopy/Paste and Save operations, a problem partially addressed via the
ClearDisplay() workaround in HotFix48.
HotFix 48:
This hotfix corrects an inability to do auto-size scanning in Memory Mode, such
as can be done with the Canon DR-2580C. It also re-fixes a problem with certain
badly-formatted JPG files (HotFix 48) to eliminate errors that were occurring in
the WorkDesk program.
In addition, this hotfix provides a workaround for a problem, currently under
investigation, with memory leaks occurring during multiple ClipboardCopy/Paste
operations between ImgEdit windows of multipage (25-300 pages) image files.
The workaround consists of an optional argument added to the
ImgEdit.ClearDisplay() method, as described below:
ClearDisplay([optional] boolean ClearCacheFile) If set to True (default is
False), the cache will be cleared for the current file, as indicated in the
ImgEdit.Image property. The workaround for the aforementioned problem requires
that this call, with ClearCacheFile=True, be issued after processing each page
of the multipage file. Note that the ImgEdit.Image property itself should not be
cleared (i.e., set to "" by the user application) until after the
ClearDisplay() call is made, since it is used to determine which cache
information is to be removed.
Note: Although this enhancement was added specifically as a workaround for the
memory leak problem, it is (and will continue to be) a generally-supported
feature for use by applications wishing to optimize cache usage or for any other
reason.
HotFix 47:
This hotfix modifies the AutoDeskew algorithm to improve processing after some
observations of some specific images experiencing deteriorating deskew quality.
This hotfix also corrects a problem with Imaging for Windows crashing when
attempting to display a certain (badly-formatted) JPG file.
HotFix 46:
This hotfix introduces a new "averaging" algorithm for scaling
of 24-bit (color) images, which eliminates problems with certain types of
images being badly displayed due to use of the "decimation"
algorithm which had been in use for image scaling prior to this hotfix.
|
|
HotFix 45:
This hotfix corrects a problem with using Imaging for Windows with
scanners having non-ANSI characters in their names, which caused
unexpected error messages when attempting to scan. It also corrects a
problem which was causing certain marks to not be resizable.
|
| |
HotFix 44:
This hotfix corrects (finally, we hope) the various problems with Kofax
Group 4 2D images created by their "Kofax standard Multi-Page TIFF
Storage Filter v3.03.000". All displayable files containing Pass Mode
coding inconsistencies should now be displayed correctly, and other Kofax
errors continue to be handled by displaying as much of the image as
possible. Other problems corrected in this hotfix include: (1) Correct
error message displayed for clipboard-full error; (2) Elimination of
excess Mark Select events; (3) Support for long (>256 character)
strings for the AnnotationText property, as well as correct processing of
Width/Height arguments for TextFromFile marks.
|
| |
HotFix 43:
This hotfix corrects the sorting of the third indexed variable of the Flow
User Input process. The sorted order of the third index now matches what
is defined by the design-time dialog interface matching the functionality
of the other index variables. This hotfix also corrects a problem with
program crashes following use of the ImgEdit DeleteAnnotationGroup()
method.
|
| |
HotFix 42:
This hotfix corrects a scanning problem which results in oversized pages
when the resolution unit is set to anything other than inches in the TWAIN
UI.
|
| |
HotFix 41:
This hotfix installs and registers the Interop Assembly (dll) file for the
Server Access Object (SAO - Imgsvacc.dll), which allows this control to be
used in the Microsoft(R) Visual Studio 2005 environment. It will be
installed only if Imaging 1.x support is already present. See HotFix 35
for additional information.
|
| |
HotFix 40:
This hotfix includes a new facility for logging TWAIN requests. It also
includes miscellaneous fixes for a recent problem with saving certain
types of TIFF JPEG image pages and with performing scaling (Zoom) when
using Fit To Selection.
|
| |
HotFix 39:
This hotfix corrects an engine-level memory overrun problem with
AutoDeskew (used in Flow) which caused a program error when processing
certain difficult-to-deskew image files. Note that this fix does NOT
address deskewing issues with such images, which continue to be badly
deskewed (or not deskewed at all) due to their difficult-to-process
content.
|
| |
HotFix 38:
This hotfix includes an enhancement to the Flow "review" dialog
box to allow selection of "Stop Processing" in addition to the
existing "Add & Continue" and "Reject/Delete"
options. Also, there is no longer a Cancel ("X") menu item on
that dialog, in order to avoid confusion due to its original
implementation having been to accept the document rather than reject it.
Other problems corrected by theis hotfix: (1) A problem with the magnifier
window being (re)positioned incorrectly after having already been created;
(2) Incorrect processing of the SetScanCapability(Image Layout) call,
which was checking for an incorrect argument count; (3) A fix to
mouse-related event processing, which in certain cases of right mouse
clicks was firing a double set of Up/Down events, possibly causing
application confusion. |
| |
HotFix 37:
This hotfix includes a change to the ImgEdit control's persistent-data
processing, which corrects a problem with the Flow/UserInput/Insert dialog
(it would sometimes not appear). Secondly, processing of Group 4 FAX
images has been changed to allow additional improperly formatted (Kofax)
scanned images to display (partially addressed in HotFixes 29 and 31).
Finally, the error logging facility has been corrected to always locate
the default log file (ImagingLog.log) in the Imaging directory; earlier
hotfixes were using the directory of whatever executable was running, so
multiple log files were being generated if the Imaging controls were being
used in programs other than the Imaging (or ImgView) application. |
| |
HotFix 36:
This hotfix includes a change to allow PCX/DCX files with incorrect image
sizes (actual rows < header-indicated rows) to be displayed. These were
formerly triggering an error message and were not displayed. This hotfix
also includes support for writing PackBits compressed TIFF images for all
image types (formerly only black&white supported), consistent with
TIFF 6.0 baseline requirements. An updated ImagingNET.pdf documentation
file for .NET installation/usage is also included in this hotfix. This
update addresses the issue of optional arguments in Visual Basic .NET,
which are handled differently from Visual Basic 6.0. |
| |
HotFix 35:
This hotfix installs and registers Interop Assembly (dll) files for the
five Imaging controls (ImgAdmin, ImgEdit, ImgOCR, ImgScan and ImgThumb),
which allows these controls to be used in the .NET 2.0 (Visual Studio
2005) environment. Interop assembly installation is enabled/disabled via
either an explicit user prompt or via command line option (+n, -n). |
| |
HotFix 34:
Includes correction of problems with the Draw() method that could result
in incorrect bounding rectangle parameters being passed to the MarkEnd
event handler. Also includes logging to additional engine-level error
events and a more condensed log format. |
| |
HotFix 33:
Includes a fix to the ImgEdit::DeleteAnnotationGroup() method that could
cause memory degradation and accesss violations, particularly when used
with long (>8) group names. |
| |
HotFix 32:
Includes support for logging of errors occurring in ImgEdit, ImgAdmin,
ImgScan, ImgOCR and ImgThumb controls. The default (primary) error log
file is ImagingLog.log in the Imaging installation directory, with
corresponding secondary log ImagingLog-save.log. Enabling/disabling of the
error logging feature, as well as non-default primary log file name and
non-default maximum log size, are found in the registry, and can be set
via the supplied EnableErrorLogging.reg and DisableErrorLogging.reg files. |
| |
HotFix 31:
Contains a workaround for additional errors encountered in certain Kofax
CCITT Group 4 2D FAX TIFF images generated by Scan Manager (extends the
HotFix 29 changes). |
| |
HotFix 30:
Contains new Server Access Object (SAO) method CreateDirectory(), which
allows users of the SAO the ability to create a file directory or document
cabinet, drawer or folder. |
| |
HotFix 29:
Contains a workaround for compression errors encountered in certain CCITT
Group 4 2D FAX TIFF images generated by Scan Manager (via Kofax TIFF
filter 3.03.000). |
| |
HotFix 28:
Corrects a error occurring when attempting to run Imaging
software/controls on the desktop when already running Imaging components
in a (background) Windows service. |
| |
HotFix 27:
Corrects a problem in which a stack overflow was occurring in certain
CCITT decompression and image scaling functions when run in a Windows
Service environment. Also corrects a problem with incorrect sizing when
doing copy/paste from one image to another image having different
resolution. Also corrects a problem with doing SaveAnnotations when an
overlay file is present. |
| |
HotFix 26:
A problem introduced in HotFix 19 caused a program failure when setting
any of the "FitTo" options before performing the scan operation.
This has been corrected. |
| |
HotFix 25:
Some LZW files created by other companies have illegal
JpegInterchangeFormat and JpegInterchangeFormatLength tags which cause
Imaging for Windows to crash. This hotfix ignores these illegal tags. |
| |
HotFix 24:
Corrects a memory leak that shows up with repeated calls to the Admin OCX
Append function. Also corrects a "hang" problem when displaying
an image containing a targeted mark and certain other annotation
combinations. |
| |
HotFix 23:
RESERVED FOR INTERNAL USE. HOTFIX NOT RELEASED. |
| |
HotFix 22:
RESERVED FOR INTERNAL USE. HOTFIX NOT RELEASED. |
| |
HotFix 21:
Added the ability to set the fill style and fill color via the
AnnotationFillStyle/Color Properties and the
SetSelectedAnnotationFillStyle/Color methods for Attach-a-Note marks. |
| |
HotFix 20:
Added ability to disable new-mark selection in ImgEdit and ImgAnno Draw()
methods.
An additional argument has been added to the Draw() methods in both the
ImgEdit and ImgAnno controls. The default action is to select the new
mark, which is consistent with past behavior. This additional argument may
be set to FALSE/TRUE or it may be omitted.
FALSE - leaves the new mark unselected and the selection state of
existing marks unchanged
TRUE - select the new mark
omitted - select the new mark
Corrected a "Cannot Save" problem with saving certain types
of multipage TIFF images. Corrected an intermittent GPF problem with OLE
Automation.
|
| |
HotFix 19:
Corrected the inability to zoom certain images to 2% zoom factor. |
| |
HotFix 18:
Corrected a printing problem where items were not printing properly. |
| |
HotFix 17:
Corrected a reported problem with the IMGEDIT SaveAnnotations method not
saving the displayed page when the REMOVE_ANNOTATIONS option was
specified. Also corrected a similar (unreported) problem with the
LoadAnnotations method. |
| |
HotFix 16:
When repeatedly drawing annotations a reduction in available resource
handles became apparent. This hotfix resolves this handle leak.
The rubber-banding of the selection rectangle is corrected.
top-left -> bottom-right
top-right -> bottom-left
bottom-left -> top-right
bottom-right -> top-left
|
| |
HotFix 15:
Added the script label and dropdown box on the font dialog box. This
allows users to select the desired script to match their font. For
example, select a eJapanesef script to coordinate with the a selected
Japanese font. |
| |
HotFix 14:
Between Jan. 20th, 2005 at around 2:54 PM and Jan. 21st, 2005 9:20 PM, if
a user tries to create a JPEG image file, the create fails with an access
violation. A similar problem would occur at regular intervals for
approximately 7 minutes every 228 days. The fix for this problem is in
oieng400.dll. |
| |
HotFix 13:
This HotFix contains new functionality. It offers the ability to
programmatically specify the text string content to be used when calling
the Draw method of the Image Edit OCX for Text and Attach-a-Note
annotations.
AnnotationText is a new property of the Image Edit OCX,. If this
property contains a string, then this string is used to specify the
content of a Text or Attach-a-Note annotation created by the Draw method
of the Image Edit OCX. During invocation for a Text or Attach-a-Note
annotation, the Draw method of the Image Edit OCX assesses the
AnnotationText property. If the property value is not an empty string,
then the property value is used to set the content of the Text or
Attach-a-Note annotation. After using the property value, the Draw method
clears the AnnotationText Property, as users are likely to remember to set
the AnnotationText property before calling Draw, but not to clear it after
use. This provides backward compatible behavior of the Draw method.
AnnotationText property
Returns or sets the text to be placed in a Text or Attach-a-Note
annotation created by the next invocation of the Draw method.
Applies To
Image Edit control
Syntax
object.AnnotationText[=desired string]
Data Type
String
Remarks
Text is placed in a Text or Attach-a-Note annotation when the Draw method
is invoked. The AnnotationText string length must be from 1 to 256,
inclusive.
|
| |
HotFix 12:
If a newer version of Internet Explorer is installed after Imaging for
Windows, or after the Imaging for Windows Hotfix, there may be a problem
running the ActiveX controls in HTML or with Microsoft Office. To resolve
this problem, either merge the registry file, activex compatibility -
restore.reg, into the system registry by double-clicking on the file or
re-install Hotfix 08 or later. This file, activex compatibility
restore.reg, is included in this Hotfix package.
Right-mouse clicking and selecting a menu item from within a selection
rectangle drawn other than upper-left to lower-right, resulted in either a
no-op operation or the message: "An internal error has
occurred."
Imaging for Windows with HotFix 12 now accepts the selection rectangle
drawn in any direction:
top-left -> bottom-right
top-right -> bottom-left
bottom-left -> top-right
bottom-right -> top-left
|
| |
HotFix 11:
On Windows XP, when running Imaging.exe maximized on the desktop, a
Windows Desktop lock no longer yields the error: "No memory is
available. The zoom operation cannot be performed." Also, the
displayed image remains intact. |
| |
HotFix 10:
Undo memory leak: After clearing part of image on multiple files or
multiple pages within a file, undo memory is not released. Memory used by
Imaging can become very large. When using the Flow output to 1x with MBCS,
the generated document names are now correct. |
| |
HotFix 09:
When using the Clear function to clear a selected image area, the entire
area is now cleared without leaving a row of pixels on the right and
bottom edges. |
| |
HotFix 08:
When using Internet Explorer releases (v5.00.2919.6307 or later), the
ActiveX controls do not work properly in HTML and with Microsoft
Office 2003. |
| |
HotFix 07:
While viewing the page properties of a 1.x document, the alt+m
functionality revealing the currently displayed page mapping now works. |
| |
HotFix 06:
Displaying and using the Magnifier with images with a mixed x and y
resolution i.e. 200 x 98, the magnifier does not scroll correctly. When
the magnifier is mid-way down the image on the page the magnifier data is
at the bottom of the image. |
| |
HotFix 05:
Attempting to display TIFF-JPEG compressed files written with the optional
Technical Note 2 (7.0) JPEGTables TIFF tag failed with "Invalid
File Format".
Pressing the delete-key in ImageEdit control, 2 KeyDown-events are
launched, then 2 KeyUp events.
Attempting to display a specific EXIF *.jpg file causes Imaging for
Windows to hang.
Thumbnail_Click event fails to fire under reproducible circumstances.
Access to a 1.x repository residing on a Windows operating system via
various means, such as a call to the DoesObjectExist method does not
work correctly and might result in an error, e.g:
"75 - Path/File access error. Unable to read or write the specified
file."
Access to a 1.x repository residing on a Windows operating system now
connects properly. This modification does not affect the
functionality for accessing a 1.x repository residing on a UNIX
operating system.
|
| |
HotFix 04:
In some cases, the Flow Output To WMS driver can generate the error:
"Invalid page type for requested function."
|
| |
HotFix 03:
After scanning a true color image, saving the image results in the error
message:
"Unable to write to this location. Possible causes are low disk
space, write
protection, or invalid filename."
|
| |
HotFix 02:
The Flow Output to WMS Driver now applies FormViews to the FormFields
dialog and only enforces the required fields that are in the applied
user's FormView(s). If a required field is not in the applied user's
FormView(s), then it is not required for Flow Output to WMS Driver
processing. |
| |
