| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Per the previous commits, this function is never called from pyatspi2
nor orca. They do monitoring of mouse events via the Registry interface.
|
|
|
|
|
|
|
|
|
| |
This function is never called from pyatspi2 nor from orca. It was
meant to be the way to register for mouse events, but that is done
with the Registry.RegisterEvent("mouse", ...) method instead.
I've turned the function into a no-op to avoid ABI breakage. We can
remove it when we have an ABI break.
|
| |
|
|
|
|
|
| |
We shouldn't call _atspi_device_listener_get_path before checking that
listener is not NULL.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mutter now has a remote desktop interface with methods to synthesize keyboard
and mouse events. This functionality has not been available through AT-SPI on
wayland since it uses X-specific functions.
Also add atspi_set_reference_window.
Probably a work in progress; doesn't appear to be behaving as intended.
Also requires that introspection be enabled on gnome-shell. Ie,
gsettings set org.gnome.shell introspect true
https://bugzilla.gnome.org/show_bug.cgi?id=709999
https://gitlab.gnome.org/GNOME/at-spi2-core/issues/14
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Atspi_register_device_event_listener and
atspi_deregister_device_event_listener take a filter (currently unused).
It can be NULL, so it should be annotated as such.
https://bugzilla.gnome.org/show_bug.cgi?id=700237
|
|\
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=688224
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=684033
|
| |
| |
| |
| |
| |
| |
| |
| | |
Atspi_registry_keystroke_listener has code to copy a keyset before passing
to dbind, in order to handle NULL keystrings, but this code was not present
in atspi_deregister_keystroke_listener.
https://bugs.freedesktop.org/show_bug.cgi?id=50578
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
If malloc returns NULL, then g_malloc will call g_error and thus abort, so
it is redundant to check the return value of g_new0 and the like, since glib
will already have aborted the program rather than returning a NULL value.
"Cleaning up" the code by removing some of these checks.
|
| |
|
|
|
|
| |
AtspiKeyListenerSyncType.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Events and DeviceEvents are now sent with transfer full to work around
a possible pygi bug.
Various other fixes.
|
| |
|
| |
|
| |
|
|
|