New in 1.5

Interactive Ink SDK 1.5 comes packed with improvements and several noticeable new features. This page provides an overview of the changes.

If you upgrade from 1.4, please take a look at the migration guide.

Improved eraser

We have reworked the eraser configuration for the sake of clarity:

  • The erase-precisely, radius and show eraser settings are now available for all parts on native. With our Web APIs, the erase-precisely is also available for "Text" and "Math" parts in WebSocket mode.

  • A new setting dynamic-radius allows the dynamic variation of the eraser radius according to the speed.

  • Eraser settings have thus changed for "Text Document", "Raw Content" and "Drawing": erase-precisely replaces erase-entire-strokes. So, if you upgrade from 1.4, make sure to check the migration guide.

  • For "Text Document", the behavior is now identical for all types of blocks. By default, the eraser precision is the object or groups of objects (stroke, character, …). It can be modified to erase portion of ink, but the precision change applies to all blocks of a "Text Document".

JIIX novelties

JIIX has evolved to version 3 to support these novelties. Please have a look at the migration guide and JIIX reference for more information.

Text layout structure

When enabling the export.jiix.text.structure property, the export file includes detailed information about the text layout structure for Text blocks, such as list items or text items within the text.

Character recognition candidates

When including the character level information by setting the export.jiix.text.chars property to true, the JIIX export file now contains a list of recognition candidates associated to characters. This will allow you to manage the character recognition candidates in the same way as the word recognition candidates.

Image data

When exporting Text documents containing images to a JIIX file, an “image” block with the image data now appears in the “Drawing” block.

More flexibility with new configuration and styling options

Diagram recognition

With iink 1.5, Diagram recognition gained new configurations:

  • diagram.convert.match-text-size. If activated, Diagram typeset text size will be computed to match handwritten ink size on convert. The diagram.convert.text-size-scale value is then used to determine the typeset: this property allows you to tune the text scale to your device screen and content. The parameter diagram.convert.match-text-size is set to false by default, which corresponds to the previous iink 1.4 behavior.
  • diagram.recognition.feedback sets the shape recognition feedback in a Diagram part or in a Diagram block within a Text Document part. Default feedback is the coloring of the shapes background with the .diagram-fill styling class pen fill color. But you can choose to have no feedback or to highlight transiently the shapes with the .diagram-anim-fill styling class pen fill color.

Diagram configuration

Diagram styling

Raw content options and styling

New styling and configuration options are available:

  • raw-content.line-pattern / text-document.raw-content.line-pattern permit the background grid display in Raw Content parts / Raw Content blocks of Text Document parts.
  • .raw-content-grid styling class can be used to customize the color of this Raw Content background grid.
  • raw-content.recognition.feedback sets the shape recognition feedback in a Raw Content part with shape recognition activated. By default, there is no feedback. But, you can choose to color the shapes background with the .raw-content-fill styling class pen fill color or to highlight transiently the shapes with the .raw-content-anim-fill styling class pen fill color.

Raw content configuration

Raw content styling

Enable/disable specific gestures

  • It is now possible to disable the slice gesture with the text-document.slice-gesture.enable setting. This gesture allows adding a freeform section as a Raw Content block into a Text Document.

  • In Raw Content parts and blocks, you can activate the scratch gesture with the gesture.raw-content.enable-scratch property.

Gestures description

Gestures support

Update to the latest MyScript technology

Interactive Ink SDK 1.5 is based on the latest version of MyScript’s core recognition SDK, resulting in recognition performance and accuracy improvements. It also improves the lexicon resources for measurement, price, literal & numerical date recognitions​.

While recognition assets provided with iink SDK 1.4 will stay compatible, you may want to update your users to the latest assets if you migrate them to 1.5.

The migration also brings the support of:

  • Checkable items:
    • The following ballot boxes can be recognized: ☐ ☑ ☒.
    • Furthermore, either on ink or already converted the ballot box ☐ can be checked with the 🗸-type mark or the x mark. The conversion will then produce the ☑ and ☒ ballot boxes.

    • On native versions, when a ballot box starts a line, tapping on it will check it with the 🗸-type mark too.
  • New symbols for all languages:
    • ✗ (ballot x),↑,↓,≠,⊕,⊖,∅,↔,≈,≥,≤, ↗︎, ↘︎,⇔,♂,♀,◦(WHITE BULLET) and ☆(WHITE STAR)​​.
    • The warning sign ⚠️ as an emoji.
  • Superscript ordinals​:
    • The following ordinals th, st, nd, rd are now supported in all languages, allowing you to recognize 1st, 2nd, 3rd, 4th and so on.
    • Additional language related superscript ordinals are also available for some latin languages.

Other changes

IEditorListener change

The native method onError has been modified to include an error code for the main ink errors made by application end users. This error code will help you customize error messages to guide your customers in their use of iink technology. If you upgrade from a previous version, make sure to read the migration guide.

If you are a newcomer, note that this callback provides detailed error messages to explain what happened. So we definitely recommend you implementing the IEditorListener interface. This will allow you both to easily debug in the integration phase, and to provide your end user with a better user experience.

iOS UIReferenceImplementation change

An iOS UIReferenceImplementation transition to Swift has started with this 1.5 release. While most of the UIReferenceImplementation code has already been moved to Swift, some code is still in Objective-C. The whole changeover to Swift requires an iink SDK API change, so it will be completed in an iink SDK future release.

We use cookies to ensure that we give you the best experience on our website Read the privacy policy