Aspose.OMR for .NET 23.3.0 - Release Notes
What was changed
Key | Summary | Category |
---|---|---|
OMRNET-712 | Added the ability to override clipping / wrapping of individual block elements (text markup / JSON markup). | New feature |
OMRNET-712 | Configurable height of block elements (text markup / JSON markup). | Enhancement |
OMRNET-712 | Configurable horizontal (left and right) padding of block elements (text markup / JSON markup). | Enhancement |
OMRNET-712 | Configurable vertical (top and bottom) padding of block elements (text markup / JSON markup). | Enhancement |
OMRNET-712 | The write-in element (text markup / JSON markup) can be configured to take up the remaining height of the parent container. | Enhancement |
Known issues and limitations
Key | Summary | Workaround |
---|---|---|
OMRNET-462 | Recognition of multi-page PDF and TIFF files causes an error. | Scan each page of the filled form into a separate file and recognize them one-by-one. |
OMRNET-555 | Recalculate method results in incorrect processing of ScoreGroup elements (text markup / JSON markup) and CustomAnswerSheet elements (text markup / JSON markup). |
Use RecognizeImage method with different threshold setting instead of run-time adjustments of recognition accuracy. |
n/a | If the block contains an element with absolute positioning (for example, an image), the block will be moved along with this element to an absolute position on the page. | Do not nest absolutely positioned elements. They should always be top-level elements in the form hierarchy. |
Public API changes and backwards compatibility
This section lists all public API changes introduced in Aspose.OMR for .NET 23.3.0 that may affect the code of existing applications.
Added public APIs:
No changes.
Updated public APIs:
The following public APIs have been updated in Aspose.OMR for .NET 23.3.0:
Block element
Compatibility: fully backward compatible.
This change will not affect existing code, print forms, or recognition results.
Block element (text markup / JSON markup) has been extended with the following new properties:
Property | Type | Default behavior | Description |
---|---|---|---|
height | integer | The height of the block is automatically adjusted to fit the content | Limit block height (in pixels). |
horizontal_padding | integer | 20 pixels | Left and right padding of the block. |
vertical_padding | integer | 20 pixels | Top and bottom padding of the block. |
overflow | clip noclip wrap |
Inherit the page settings | How to clip and wrap elements inside the block:
Overflow page setting. |
Write-in element
Compatibility: fully backward compatible.
This change will not affect existing code, print forms, or recognition results.
The boolean adaptive
property has been added to write-in element (text markup / JSON markup). Possible values:
false
(default) - the write-in element has a fixed height, as in previous releases.true
- the write-in element takes up the remaining height of the parent container.
Removed public APIs:
No changes.
Usage examples
See the examples below to learn more about the changes introduced in this release:
Adaptive write-in height
?container=
columns_count=3
?block=
column=1
border=square
border_color=black
border_size=10
height=200
overflow=noclip
vertical_padding=0
horizontal_padding=0
?write_in=
hint=custom write-in text
font_style=bold
color=red
font_size=9
font_family=Times new Roman
adaptive=true
&block
?block=
column=2
border=square
border_color=black
border_size=10
height=200
overflow=noclip
?write_in=
hint=custom write-in text
font_style=bold
color=red
font_size=9
font_family=Times new Roman
adaptive=true
&block
?block=
column=3
border=square
border_color=black
border_size=10
height=200
overflow=noclip
vertical_padding=40
horizontal_padding=40
?write_in=
hint=custom write-in text
font_style=bold
color=red
font_size=9
font_family=Times new Roman
adaptive=true
&block
&container
Block size and padding
?container=
?block=
border=square
border_color=black
border_size=1
height=200
vertical_padding=30
horizontal_padding=10
?paragraph=
?content=It is not down on any map; true places never are.
¶graph
&block
&container