The "text-attributes-changed" signal is emitted when the text attributes of the text of an object which implements AtkText changes.
The "text-caret-moved" signal is emitted when the caret position of the text of an object which implements AtkText changes.
The "text-changed" signal is emitted when the text of the object which implements the AtkText interface changes, This signal will have a detail which is either "insert" or "delete" which identifies whether the text change was an insertion or a deletion.
The "text-insert" signal is emitted when a new text is inserted. If the signal was not triggered by the user (e.g. typing or pasting text), the "system" detail should be included.
The "text-remove" signal is emitted when a new text is removed. If the signal was not triggered by the user (e.g. typing or pasting text), the "system" detail should be included.
The "text-selection-changed" signal is emitted when the selected text of an object which implements AtkText changes.
Adds a selection bounded by the specified offsets.
Get the ranges of text in the specified bounding box.
Gets the offset of the position of the caret (cursor).
Gets the specified text.
Gets the character count.
Get the bounding box containing the glyph representing the character at a particular text offset.
Creates an AtkAttributeSet which consists of the default values of attributes for the text. See the enum AtkTextAttribute for types of text attributes that can be returned. Note that other attributes may also be returned.
Gets the number of selected regions.
Gets the offset of the character located at coordinates x and y. x and y are interpreted as being relative to the screen or this widget's window depending on coords.
Get the bounding box for text within the specified range.
Creates an AtkAttributeSet which consists of the attributes explicitly set at the position offset in the text. start_offset and end_offset are set to the start and end of the range around offset where the attributes are invariant. Note that end_offset is the offset of the first character after the range. See the enum AtkTextAttribute for types of text attributes that can be returned. Note that other attributes may also be returned.
Gets the text from the specified selection.
Gets a portion of the text exposed through an AtkText according to a given offset and a specific granularity, along with the start and end offsets defining the boundaries of such a portion of text.
the main Gtk struct as a void*
Gets the specified text.
Gets the specified text.
Gets the specified text.
Gets the specified text.
Get the main Gtk struct
Removes the specified selection.
Makes text visible on the screen by scrolling all necessary parents.
Makes an object visible on the screen at a given position by scrolling all necessary parents.
Sets the caret (cursor) position to the specified offset.
Changes the start and end offset of the specified selection.
Get the AtkTextAttribute type corresponding to a text attribute name.
Gets the name corresponding to the AtkTextAttribute
Gets the value for the index of the AtkTextAttribute
Associate name with a new AtkTextAttribute
Frees the memory used by an AtkAttributeSet, including all its AtkAttributes
Frees the memory associated with an array of AtkTextRange. It is assumed that the array was returned by the function atk_text_get_bounded_ranges and is NULL terminated.
AtkText should be implemented by AtkObjects on behalf of widgets that have text content which is either attributed or otherwise non-trivial. AtkObjects whose text content is simple, unattributed, and very brief may expose that content via atk_object_get_name instead; however if the text is editable, multi-line, typically longer than three or four words, attributed, selectable, or if the object already uses the 'name' ATK property for other information, the AtkText interface should be used to expose the text content. In the case of editable text content, AtkEditableText (a subtype of the AtkText interface) should be implemented instead.
AtkText provides not only traversal facilities and change notification for text content, but also caret tracking and glyph bounding box calculations. Note that the text strings are exposed as UTF-8, and are therefore potentially multi-byte, and caret-to-byte offset mapping makes no assumptions about the character length; also bounding box glyph-to-offset mapping may be complex for languages which use ligatures.