summaryrefslogtreecommitdiff
path: root/gtk/gtkaccessibleprivate.h
Commit message (Collapse)AuthorAgeFilesLines
* a11y: Documentation and code style fixesEmmanuele Bassi2023-02-031-1/+28
|
* Add versioned symbol annotationsEmmanuele Bassi2023-02-031-0/+5
|
* Make GtkAccessible publicLukáš Tyrychtr2023-02-031-31/+0
| | | | | | | Out of tree classes need to be able to implement the GtkAccessible interface, in order to implement custom accessible objects. Fixes: #4240
* a11y: Add bounds rectangle to GtkAccessibleLukáš Tyrychtr2023-02-031-0/+5
| | | | | | | | | | Make the bounds calculation part of the accessible interface. Bounds are used by ATs like Orca to implement features like Flat Review: https://help.gnome.org/users/orca/stable/howto_flat_review.html.en Or to determine the area of a non-presentational widget.
* a11y: Add DOM-like API to GtkAccessibleLukáš Tyrychtr2023-02-031-0/+7
| | | | | Add get_parent and get_child_at_index to GtkAccessible so we can decouple the a11y tree from the widget tree.
* Introduce GtkAccessibleRangeLukáš Tyrychtr2022-09-291-0/+2
| | | | This introduces GtkAccessibleRange, an interface which allows the accessibility backend to work with a control which can adjust a value.
* a11y: Add child state change to GtkATContextEmmanuele Bassi2020-10-211-0/+4
| | | | | And the required private API in GtkAccessible to notify AT contexts of changes in the children list.
* a11y: Add bounds change apiMatthias Clasen2020-10-191-0/+2
| | | | | Add a way for GTK to pass bounds change information to the AT context.
* CosmeticsMatthias Clasen2020-10-191-2/+2
|
* accessible: Add gtk_accessible_get_platform_stateMatthias Clasen2020-10-121-2/+7
| | | | | | | | | | As a companion to go with the platform_change api, add a gtk_accessible_get_platform_state() function that can be used by backends to get the platform state. This is in preparation for making entries inherit their focus states from the text widget within.
* accessible: Add a way to hide accessiblesMatthias Clasen2020-10-121-0/+2
| | | | | | | | | | | | | | | | Similar to gtk_widget_should_layout(), add a gtk_accessible_should_present() function that backends can use to determine whether an accessible should be presented or not. Ways to make a widget not presented in a11y: - hide the widget - set its role to NONE - make it have a NULL AT context We will use this in future to hide the GtkText inside an entry, since the Text implementation will be done by the wrapper.
* CosmeticsMatthias Clasen2020-10-121-2/+2
|
* a11y: Pass on platform changesMatthias Clasen2020-10-121-1/+4
| | | | | | | | | | | | | Add an enum for 'platform changes' to the at context change notification mechanism. This will let us pass along things that ARIA considers 'platform state' such as focus or editability. The difference between the platform state and other ARIA states is that we don't keep the platform state separately in the at context - backends are expected to just query the widgets. This is just about avoiding notify listeners for change notification.
* a11y: Turn accessible roles to stringEmmanuele Bassi2020-10-121-0/+3
| | | | | Add a simple utility function to turn GtkAccessibleRole values into the appropriate string, including localization.
* Plug GtkATContext into GtkAccessibleEmmanuele Bassi2020-07-261-0/+37
| | | | | | An Accessible implementation must create an ATContext object. UI elements are supposed to interact with the GtkAccessible API, but we expose GtkATContext to allow patterns like delegation.
* Drop private GtkAccessible apiMatthias Clasen2011-07-141-31/+0
| | | | We no longer use factories anywhere.
* Add a private function for accessible factory registrationMatthias Clasen2011-02-171-0/+31
This avoids repeating the same code for each widget that has its own accessible implementation inside GTK+.
View Lorry Controller Status