Click or drag to resize

RecognitionContext Class

Recognition Context
Inheritance Hierarchy
SystemObject
  Scandit.RecognitionRecognitionContext

Namespace:  Scandit.Recognition
Assembly:  Scandit.Recognition (in Scandit.Recognition.dll) Version: 5.18.0.10 (5.18.0.10)
Syntax
public class RecognitionContext : IDisposable

The RecognitionContext type exposes the following members.

Constructors
  NameDescription
Public methodRecognitionContext(String, String)
Create a new context for recognition
Public methodRecognitionContext(String, String, String)
Create a new context for recognition.
Top
Properties
  NameDescription
Public propertyStatic memberVersion
Top
Methods
  NameDescription
Public methodDispose
Disposes the RecognitionContext
Public methodEquals
Determines whether the specified object is equal to the current object.
(Inherited from Object.)
Protected methodFinalize
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.
(Inherited from Object.)
Public methodGetHashCode
Serves as the default hash function.
(Inherited from Object.)
Public methodGetType
Gets the Type of the current instance.
(Inherited from Object.)
Protected methodMemberwiseClone
Creates a shallow copy of the current Object.
(Inherited from Object.)
Public methodSetGeographicalLocation
Set the geographical location.
Public methodStartFrameSequence
Start a new frame sequence
Public methodToString
Returns a string that represents the current object.
(Inherited from Object.)
Top
Remarks

The 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 Information

Supported in: 1.0
See Also