Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Aspose.OMR allows you to describe the layout and content of an OMR form directly in the application code. Although it takes much more coding than generating forms from text or JSON sources, this approach works best when you need to design forms with personalized fields such as a respondent’s name or a unique QR code.
The form is described as an instance of TemplateConfig
class. All internal elements are nested inside this object.
You must also define at least one page as an instance of PageConfig
class.
Reference Aspose.OMR.Generation.Config
and Aspose.OMR.Generation.Config.Elements.Parents
namespaces to use TemplateConfig
and PageConfig
types without specifying the fully qualified namespace:
using Aspose.OMR.Generation.Config;
using Aspose.OMR.Generation.Config.Elements.Parents;
The following code generates an empty single-page OMR form:
TemplateConfig templateConfig = new TemplateConfig() {
Children=new List<BaseConfig>() {
new PageConfig() {
Children = new List<BaseConfig>() {
/*
* Describe form content here
*/
}
}
}
};
You can use multiple PageConfig
objects to separate the content of a large form into several pages.
Aspose.OMR offers a wide range of elements that allow you to create forms of any complexity - from a simple ballot to high school exam papers and finance application checklists.
Check out code examples to see how different elements can be used and combined with each other.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.