| AtkText {RGtk2} | R Documentation |
The ATK interface implemented by components with text content.
atkTextGetText(object, start.offset, end.offset)
atkTextGetCharacterAtOffset(object, offset)
atkTextGetTextAfterOffset(object, offset, boundary.type)
atkTextGetTextAtOffset(object, offset, boundary.type)
atkTextGetTextBeforeOffset(object, offset, boundary.type)
atkTextGetCaretOffset(object)
atkTextGetCharacterExtents(object, offset, coords)
atkTextGetRunAttributes(object, offset)
atkTextGetDefaultAttributes(object)
atkTextGetCharacterCount(object)
atkTextGetOffsetAtPoint(object, x, y, coords)
atkTextGetBoundedRanges(object, rect, coord.type, x.clip.type, y.clip.type)
atkTextGetRangeExtents(object, start.offset, end.offset, coord.type)
atkTextGetNSelections(object)
atkTextGetSelection(object, selection.num)
atkTextAddSelection(object, start.offset, end.offset)
atkTextRemoveSelection(object, selection.num)
atkTextSetSelection(object, selection.num, start.offset, end.offset)
atkTextSetCaretOffset(object, offset)
atkTextAttributeRegister(name)
atkTextAttributeGetName(attr)
atkTextAttributeForName(name)
atkTextAttributeGetValue(attr, index)
GInterface +----AtkText
AtkText is implemented by
AtkNoOpObject.
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 atkObjectGetName 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.
AtkText
AtkTextRangeAtkTextRange is a transparent-type.
boundsAtkTextRectangle] A rectangle giving the bounds of the text rangestart_offsetend_offsetcontent
AtkTextRectangleAtkTextRectangle is a transparent-type.
xywidthheight
AtkAttributeAtkAttribute is a transparent-type.
nameatk\Text\Attr\Get\Name()valueatk\Text\Attr\Get\Value() for those which are strings.
For values which are numbers, the string representation of the number
is in value.
AtkTextBoundarycharword-startword-endsentence-startsentence-endline-startline-end
AtkTextClipTypenoneminmaxboth
AtkTextAttributeinvalidleft-marginright-marginindentinvisibleeditablepixels-above-linespixels-below-linespixels-inside-wrapbg-full-heightriseunderlinestrikethroughsizescaleweightlanguagefamily-namebg-coloru,u,u"fg-coloru,u,u"bg-stippleGdkBitmap is set for stippling the background color.fg-stippleGdkBitmap is set for stippling the foreground color.wrap-modedirectionjustificationstretchvariantstylelast-defined
text-attributes-changed(atktext, user.data)atktextAtkText] the object which received the signal.user.data
text-caret-moved(atktext, arg1, user.data)atktextAtkText] the object which received the signal.arg1user.data
text-changed(atktext, arg1, arg2, user.data)atktextAtkText] the object which received the signal.arg1arg2user.data
text-selection-changed(atktext, user.data)atktextAtkText] the object which received the signal.user.data
Derived by RGtkGen from GTK+ documentation
http://developer.gnome.org/doc/API/2.0/atk/AtkText.html