Other Divider Considerations

Consider the following when deciding when and how to use the Divider object in an application:

• The Divider object is designed to separate drawings and blocks of handwriting, but not to recognize higher levels of structure, such as tables or columns.
• The Divider object does not provide interfaces specifically for correction of results of layout analysis.
• The use of timeout and number of stroke heuristics to add or remove multiple strokes at a time from the strokes in the Divider object may improve performance.

Reanalysis Considerations

If you are considering using the Divider object in an application where the Divider object may have to reanalyze large amounts of ink, keep the following in mind.

Retaining Copies of Ink and Strokes

An application can keep copies of Ink and DivisionResult objects for application elements that may be revisited later in the application session. This eliminates the need to reanalyze the Ink object if the user returns to the element. This approach trades off memory for better performance.

Data Reduction Heuristics

You may be able to record the analysis results as application data, and implement heuristics to determine when to reanalyze a set of strokes. This practice would reduce the need to reanalyze all the ink in the application between application sessions. However, care must be taken to preserve structural element boundaries or to reanalyze all the strokes for affected elements.

Related topics

InkDivider Class

Microsoft.Ink.Divider Class