NuGet
dotnet add package Solidsoft.Reply.BarcodeScanner.Calibration
The following changes were made in this release:
Fixed incompatibilities between versions for .NET 6.0 and .NET 7.0 or later.
Introduced in previous versions:
v2.2.16: Fixed pre-processor issue that prematurely processed carriage return and line feed characters.
v2.2.15: Further improvements to advice reporting.
v2.2.14: Fixed issue with reporting Format 05/Format 06 reliability. Improvements to advice reporting.
v2.2.13: Implemented support for detecting issues with EOT characters. Improved handling for ASCII control characters used in ISO/IEC 15434 messages.
v2.2.12: Fixed issue with EDI-related advice - was being shown when Format 05/06 tests were not selected.
v2.2.11: Introduction of handling for EOT (ASCII 04) characters in ISO/IEC 15434-encoded barcodes (Format 05 and Format 06). This was originally omitted over fears of possible network issues when transmitting EOT characters. These fears have proved unfounded, and the lack of EOT analysis conflicted with reliable detection of suffixes. Improved handling for File and Unit separator characters used in EDI data in ISO/IEC 15434-encoded barcodes (Format 05 and Format 06). These are now handled individually, improving the advice given in certain circumstances. Fixes to various issues with localised resource.
v2.2.10: Improved recording of ambiguities involving AIM identifiers.
v2.2.9: Fixed issue with calculation of scanner capabilities for ISO/IEC 15434 data.
v2.2.8: Implemented improved handling for situations where ambiguities exist for EDI control characters with characters that are not used in EDI data.
v2.2.7: Updated an advice message to describe the condition fully. Introduced minor improvement to aid debugging in scenarios where unidentified keys are not reported correctly to the calibrator.
v2.2.6: Fixed an issue where scanner dead keys were incorrectly interpreted as ligatures.
v2.2.5: Added support for reporting the barcode scanner performance in characters per second. Fixed an issue where the Calibrator would incorrectly infer that the scanner is compensating for Caps Lock. Fixed an issue where, when an ambiguity occurs for a control character, a character map entry is incorrectly created. Improved the advice handling for EDI issues.
v2.2.4: Updated packages.
v2.2.3: Fixed additional issues with ISO/IEC 15434 separator handling to ensure that the correct advice is output. Fixed issues with matches between dead keys in scanner and computer keyboard layouts.
v2.2.2: Improvements made to eliminate ISO/IEC 15434-related warnings if no assessment is made for Format 05 and Format 06 barcodes. Previously, the calibrator would report issues for ASCII 30 (Record Separator) and EDI-related issues even if the calibrator was configured to only assess capabilities for scanning FNC1 and GS1-128 barcodes. This change eliminates potential sources of confusion for users who are not interested in assessing ISO/IEC 15434 capabilities.
v2.2.1: Fixed a bug that could affect dead key recognition where the scanner and computer keyboard layouts match and a literal dead key is entered. This was detected when testing Estonian keyboard layouts. The bug caused the calibrator to output redundant character mappings.
v2.2.0: Added a new feature that controls the assessment of the script supported by the configured computer keyboard layout. Sometimes, we want to supress this assessment - e.g., if a pre-processor represents characters differently to the configured keyboard. For example, the built-in AIDC DOM event code processor outputs characters drawn from across UNICODE which can lead to incorrect assessment of the keyboard script. This is a non-breaking change that introduces a new optional parameter on the Calibrate method.
v2.1.1: Fixed issue in which some system capabilities were prematurely reset to default values when calibration fails.
v2.1.0: Amendment to provide system capabilities output in the event that dead key barcodes are skipped. When using the Calibrator to analyse barcode-computer interaction, only (i.e., if we are not interested in using the calibration data to parse actual unique identifiers), it is useful to allow end users to skip scanning the dead key barcodes. We collect enough analytics on the Baseline barcode scan to indicate major issues, and we don't need to know about every potential ambiguity, although there is a risk that the Calibrator will only identify a keyboard mismatch, but not report incompatibility. Small change to improve handling of ligatures. The code assumes that ligatures will never conflict with other data - e.g., a ligature for 'Æ' would never conflict with an 'a' followed by an 'e'. This is generally true because of
the use of UNICODE combining characters, but it is not guaranteed. The library currently cannot handle such situations correctly, and there is no very obvious way to fix this (there may be heuristic approach, though). However, investigation of the issue did reveal another bug when this situation is encountered which we have fixed.