Leadtools.Forms.Processing Requires Document/Medical product license | Send comments on this topic. | Back to Introduction - All Topics | Help Version 16.5.9.25
OmrFormFieldResult Class
See Also  Members  
Leadtools.Forms.Processing Namespace : OmrFormFieldResult Class



Provides the results of processing the OMR field.

Syntax

Visual Basic (Declaration) 
<SerializableAttribute()>
Public Class OmrFormFieldResult 
   Inherits OcrFormFieldResult
Visual Basic (Usage)Copy Code
Dim instance As OmrFormFieldResult
C# 
[SerializableAttribute()]
public class OmrFormFieldResult : OcrFormFieldResult 
C++/CLI 
[SerializableAttribute()]
public ref class OmrFormFieldResult : public OcrFormFieldResult 

Example

For example, refer to the FormFieldResult example.

Remarks

Fields are defined for each page in the processing engine. All fields require you fill in the Property specifying where the field is located, and a Name Property.

Fields can be added or retrieved through the FormProcessingEngine.Pages property. Once fields are defined, they can be loaded/saved from disk using the FormProcessingEngine.LoadFields(String) and FormProcessingEngine.SaveFields(String) methods, allowing you to define MasterForm fields just once and save them to disk. LEADTOOLS supports TextFormField, OmrFormField, BarcodeFormField, ImageFormField, and custom user-defined fields derived from FormField. When obtaining processing results, you should check for the type of each field, and cast it to the appropriate type in order to obtain the field specific results (barcode, image, etc).

Inheritance Hierarchy

System.Object
   Leadtools.Forms.Processing.FormFieldResult
      Leadtools.Forms.Processing.OcrFormFieldResult
         Leadtools.Forms.Processing.OmrFormFieldResult

Requirements

Target Platforms: Microsoft .NET Framework 3.0, Windows XP, Windows Server 2003 family, Windows Server 2008 family

See Also

Leadtools.Forms requires a Forms Module license and unlock key. For more information, refer to: Imaging Pro/Document/Medical Features