| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
This method is still used, but is in the process of deprecation by the
atspi-device-listener functions.
I'm documenting it to have a reference of what the dbus demarshalling
code is supposed to do.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I ran this on each directory with C files:
clang-format -i *.[ch]
"-i" is the in-place option.
I also adjusted the order of #includes for some files which failed to
build after that:
Clang-format reorders blocks of #include directives alphabetically,
but they can be grouped and separated by blank lines. If there is a
blank line between blocks, like
#include "zork.h"
#include "bar.h"
#include "foo.h"
then it will not put zork.h after the other two. The last two header
files will be sorted alphabetically.
We can adjust the formatting of chunks of code by hand with comments
like these:
/* clang-format off */
this code {
is, formatted, by, hand;
}
/* clang-format on */
See https://clang.llvm.org/docs/ClangFormat.html for the general
manual and https://clang.llvm.org/docs/ClangFormatStyleOptions.html
for the style options and the comments described above.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is intended to replace the registry-based method for capturing
keystrokes. It is needed because gtk 4 no longer sends key notifications
in a way that atk-bridge can process them. Unlike the original API, key
grabs are separated from key notifications. Clients wishing to consume
keystrokes must proactively register a grab for the given key. Currently,
there is a backend for X11 and an unfinished legacy back end using the old
registry-based method. Hopefully, there will be a mutter/wayland back end in
the future, but we need to define a protocol there first.
|
| |
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/2
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Normally, this is set to the application / root accessible from the
application corresponding to the event source, but screen-reader-generated
events are actually generated by the screen reader. The sender is set based on
the application that sent the signal over dbus, so, in the latter case, this
will be set to the screen reader.
Per discussion at https://gitlab.gnome.org/GNOME/orca/issues/36
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
atspi/Makefile.am
atspi/atspi-accessible.c
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Generate enum types where appropriate.
Fix prototypes where a method took a "gint" that was really a bitflag.
Remove tables of state and role names, since these are now redundant with data
from the generated enums and would need to be maintained in parallel.
These changes were originally in master but have been backed out since they
break compatibility with pygobject 2.26.0, which some users are still using.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit a12d7458110c57e183916255d701b1e0d7c070e1.
Conflicts:
atspi/atspi-constants.h
Reverting these enum clean-ups for now, since they require pygobject 2.28.0
for pyatspi, at least one user is pulling git while using pygobject 2.26.0,
upgrading pygobject is likely to be a complicated process that may break
things, and these changes are only code clean-ups that will not really benefit
users. Will reinstate in a separate branch and merge some time in the future.
|
| |
|
|
|
|
|
| |
Use glib-enums to generate GTypes for enums, and modify enum definitions so
that they will be marked as bitflags where appropriate. This helps with
introspection and allows functions that take flags to be prototyped as such
rather than being marked as taking a gint.
|
| |
|
|
| |
This reverts commit 1e08268e94a4143f4b6f4bd29e08c9f1a868bb45.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
AtspiAccessible is now derived from a base class called AtspiObject which
defines the object's application and object path, since this is common with
AtspiHyperlink.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
