Pegasus Imaging's OCR Xpress v2 FAQ's

OCR Xpress v2 FAQ

Q1: How can I determine if I have the latest version of a Pegasus control?

Q2: How do I distribute my application?

Q3: What DLL’s do I need to distribute with my application?

Q4: Are there any known issues with OCR Xpress v2?

Q1: How can I determine if I have the latest version of a Pegasus control?

Please download the PegConnect utility program from the following link: PegConnect
or reference the Latest Builds page.

Q2: How do I distribute my application?

Please note: You must have received unlock codes in order to distribute applications. These are received when runtimes are purchased. If you have not received them please Contact Sales.

1) If you are using the .NET interface you must call the UnlockRuntime method in the Licensing class where the application begins and pass the unlock codes as the parameters. For example:

ocrXpress2.Licensing.UnlockRuntime(1234, 1234, 1234, 1234);

2) If you are using the ActiveX control you must call the UnlockRuntime method where your application begins and pass the unlock codes as the parameters. For example:

OCRXpress2.UnlockRuntime 1234,1234,1234,1234

Q3: What DLL’s do I need to distribute with my application?

1) If you are using the ActiveX interface please distribute the following DLL:

PegasusImaging.ActiveX.OcrXpress2.dll

Please Note: You must register the PegasusImaging.ActiveX.OcrXpress2.dll via your installation program or manually via the regsvr32.exe utility.

2) If you are using the .NET interface please distribute the following DLL:

PegasusImaging.Winforms.OcrXpress2.dll

Q4: Are there any known issues with OCR Xpress v2?

Please note there are 2 known issues when using the current release of the OCRXpress v2 product as detailed below. Pegasus Imaging will resolve these 2 issues in the first service release of OCRXpress v2.

1) There is a threading issue when running multiple threads when each thread creates its own OCRXpress object. When under heavy load, one thread may hang and subsequently hang the other threads.

2) There is an issue with approximate matching where setting the number of maximum deletions to zero affects the behavior of matching when insertions are involved. For example, the following example demonstrates the issue:

    TestPattern = "1234567890";
    TestString = "1234abcd567890";
    MaximumInsertions = 4;
    MaximumDeletions = 0;
    MaximumSubstitutions = 6;
    MaximumError = 10;
    match result = 1234abcd5;

As a workaround the MaximumDeletions property can be set to a value greater than 0 and then the match result will be the expected value of: 1234abcd567890.

Please contact support@jpg.com if you have any further questions.