RecognitionContext Class |
Inheritance HierarchyNamespace: Scandit.Recognition
Assembly: Scandit.Recognition (in Scandit.Recognition.dll) Version: 5.19.3.10 (5.19.3.10)
SyntaxThe RecognitionContext type exposes the following members.
Constructors| Name | Description | |
|---|---|---|
 | RecognitionContext(String, String) | Create a new context for recognition |
| RecognitionContext(String, String, String) |
Create a new context for recognition.
|
Properties
Methods| Name | Description | |
|---|---|---|
| Dispose | Disposes the RecognitionContext |
| Equals | Determines whether the specified object is equal to the current object. (Inherited from Object.) |
 | Finalize | Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) |
| GetHashCode | Serves as the default hash function. (Inherited from Object.) |
| GetType | Gets the Type of the current instance. (Inherited from Object.) |
| MemberwiseClone | Creates a shallow copy of the current Object. (Inherited from Object.) |
| SetGeographicalLocation | Set the geographical location. |
| StartFrameSequence |
Start a new frame sequence
|
| ToString | Returns a string that represents the current object. (Inherited from Object.) |
RemarksThe recognition context manages scanner objects of different types and takes care of scheduling the recognition process. By default, the recognition context does not have any scanners. To recognize a particular set of objects, the scanner object must be created. At the moment, the only available scanner is the BarcodeScanner which recognizes 1d and 2d codes in images.
To create a new recognition context a platform-specific function must be used. These functions take care of license-management read the appropriate system properties to optimize the recognition process for the device.
For performance reasons it is recommended that only one context per application is used. If multiple contexts are created, make sure that context with different device model names do not share the same writable_data_path. Contexts with the same device model name can share the writeable data path.
Version InformationSupported in: 1.0
See Also