summaryrefslogtreecommitdiff
path: root/atspi/atspi-device-legacy.c
Commit message (Collapse)AuthorAgeFilesLines
* Hold a reference to the AtspiDevice while processing eventsHEADmainMike Gorse2023-05-171-0/+2
| | | | | If this is not done, then the device might be finalized from under us during a callback, leading to a crash.
* Reformat all the *.[ch] files with clang-formatFederico Mena Quintero2022-12-061-47/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Add an "announcement" event/signal to allow objects to send notificationsMike Gorse2022-08-041-1/+1
| | | | Fixes #63
* Reorder g_free around g_slist_removeFederico Mena Quintero2021-12-141-1/+1
| | | | To avoid using a freed pointer. It's harmless, but static-scan complains.
* AtspiDevice key grab fixesMike Gorse2021-05-121-2/+14
|
* AtspiDeviceListenerCB: remove const from event prototypeMike Gorse2021-02-231-1/+2
| | | | | | | | The parameter is marked with (transfer full), and the code expects the caller to free the event, so adjust the prototype to clarify the expected behavior. Also fix a related memory leak in atspi-device-legacy.c. Fixes #31
* Device fixesMike Gorse2021-01-271-2/+227
|
* Add device APIMike Gorse2021-01-111-0/+91
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.