| 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.
|
| | |
|
| |
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/2
|
| | |
|
| |
|
|
| |
Error logs has different naming convention in atspi/ files.
|
| |
|
|
|
|
|
|
| |
We shouldn't assume that we own the list of interfaces passed in.
The caller may free the list, and then we have a pointer to invalid
data in the AtspiMatchRule structure, causing crashes.
https://bugzilla.gnome.org/show_bug.cgi?id=734805
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add atspi_event_listener_register_full, to request that particular data
be sent with an event, and cache the data for the duration of the event
callback.
This also extends the D-Bus protocol, adding an a{sv} to an event to send
this data along, but we will still read events without this array added for
backwards compatibility (and compatibilllity with QT-AT-SPI, which does not
send this data for now).
https://bugzilla.gnome.org/show_bug.cgi?id=708695
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=700865
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It is not safe to ref a hash marked (transfer none) and expect its elements
to remain, since the caller will assume that it owns the elements and may
deallocate them (this is done by pygobject). It would also be problematic
to simply mark the hash (transfer full), since we need to either assume that
the caller passed a destroy function when creating the hash (pygobject does
not) or deallocate the values ourselves when the match rule is finalized
(which requires making assumptions about the correct free function needed to
deallocate the values that the caller allocated). So it seems that the only
safe thing to do is to copy the hash.
|
| | |
|
| |
|
|
|
|
|
| |
Objects are now "disposed" when RemoveAccessible is received or the application
goes away. This allows the objects to be dereferenced and properly cleaned up.
Also fix some related bugs and add i18n.
Some reference leaks remain, however.
|
| | |
|
| |
|
