This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
This section contains information about the programming elements used with the Text Object Model (TOM).
The TOM defines a substantial set of text manipulation interfaces. Text solutions such as Microsoft Word and rich edit controls support the TOM feature set. TOM was greatly influenced by WordBasic (the programming language used for Word) and it is easy to use from Microsoft Visual Basic for Applications (VBA). This compatibility has several advantages:
However, it can be less efficient for C/C++ purposes than the use of more general lower level COM interfaces.
TOM is a straightforward set of interfaces to implement for its primary text solutions, Word and rich edit controls. However, for applications that place minor emphasis on text, it is better to provide TOM interfaces by transferring the text to an edit control that supports TOM. Since rich edit controls ship with Microsoft operating systems, they are the standard means of obtaining TOM functionality.
| Topic | Contents |
|---|---|
| About Text Object Model | The top-level Text Object Model (TOM) object is defined by theITextDocument interface, which has methods for creating and retrieving objects lower in the object hierarchy. |
| Using The Text Object Model | The code samples in this document show various aspects of using the Text Object Model (TOM). |
| Topic | Contents |
|---|---|
| ITextDocument | TheITextDocument interface is the TOM top-level interface, which retrieves the active selection and range objects for any story in the document whether active or not. It enables the application to:
When to Implement Applications typically do not implement theITextDocument interface. Microsoft text solutions, such as rich edit controls, implementITextDocument as part of their TOM implementation. When to Use Applications can retrieve anITextDocument pointer from a rich edit control. To do this, send anEM_GETOLEINTERFACE message to retrieve anIRichEditOle object from a rich edit control. Then, call the object'sIUnknown::QueryInterface method to retrieve anITextDocument pointer. |
| ITextFont | TOM rich text-range attributes are accessed through a pair of dual interfaces,ITextFont andITextPara. |
| ITextPara | TOM rich text-range attributes are accessed through a pair of dual interfaces,ITextFont andITextPara. |
| ITextRange | TheITextRange objects are powerful editing and data-binding tools that allow a program to select text in a story and then examine or change that text. |
| ITextSelection | A text selection is a text range with selection highlighting. |
| ITextStoryRanges | The purpose of theITextStoryRanges interface is to enumerate the stories in anITextDocument. |
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?
Was this page helpful?
Want to try using Ask Learn to clarify or guide you through this topic?