| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
gcc has optimizations for include guards that only work
if they are outermost in the the header.
https://bugzilla.gnome.org/show_bug.cgi?id=689810
|
| |
|
|
| |
More preparation for installing these headers.
|
| |
|
|
|
|
|
| |
Since we are going to install these headers soon, we need
to make their mutual includes work in the installed location
as well. Also, avoid including individual gtk headers, to
avoid trouble with single-include guards.
|
| |
|
|
| |
Replace GAIL in top comments by 'GTK+ - accessibility implementations'.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit exposes the get_type() functions and standard
headers for accessible implementations. This makes it possible
to derive from the GTK accessible implementations without
GType magic tricks. This is necessary, because we require the
a11y type hierarchy to be parallel to the widget type hierarchy.
So, if you derive a widget and need to adjust its a11y implementation,
you have to be able to derive its accessible implementation.
This commit probably exposes more than is absolutely necessary,
it also exposes accessibles of widgets that are unlikely candidates
for deriving from.
|
| |
|
|
|
| |
These are not used currently. Just put them in now in
case we need them in the future.
|
| | |
|
| |
|
|
|
| |
_-prefix most of the get_type functions in a11y/.
There are still some more symbols left.
|
| | |
|
|
|
While doing this, drop the get_mdi_zorder implementation
that really should come from the window manager side. Dropping
this saves some 500 lines.
|
