Add the specified handler to the set of functions to be called when this object receives focus events (in or out). If the handler is already added it is not added again
The 'bounds-changed" signal is emitted when the bposition or size of the component changes.
Checks whether the specified point is within the extent of the component.
Returns the alpha value (i.e. the opacity) for this component, on a scale from 0 (fully transparent) to 1.0 (fully opaque).
Get the main Gtk struct
Gets the rectangle which gives the extent of the component.
Gets the layer of the component.
Gets the zorder of the component. The value G_MININT will be returned if the layer of the component is not ATK_LAYER_MDI or ATK_LAYER_WINDOW.
Gets the position of component in the form of a point specifying component's top-left corner.
Gets the size of the component in terms of width and height.
Grabs focus for this component.
Gets a reference to the accessible child, if one exists, at the coordinate point specified by x and y.
Remove the handler specified by handler_id from the list of functions to be executed when this object receives focus events (in or out).
Makes component 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 extents of component.
Sets the position of component.
Set the size of the component in terms of width and height.
AtkComponent should be implemented by most if not all UI elements with an actual on-screen presence, i.e. components which can be said to have a screen-coordinate bounding box. Virtually all widgets will need to have AtkComponent implementations provided for their corresponding AtkObject class. In short, only UI elements which are *not* GUI elements will omit this ATK interface.
A possible exception might be textual information with a transparent background, in which case text glyph bounding box information is provided by AtkText