| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
translation sprint
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the past, a gtk button's do_action handler added an idle to invoke
the button and then returned, but now the idle has been removed, and the
do_action call activates the button directly, meaning that, if the
button invokes a dialogue, then atk_action_do_action will not return
until the dialog closes. So, to be safe, we need to send a reply before
invoking atk. This means that atk's return value gets ignored, although
it was somewhat meaningless in gtk's case anyhow. This required that
droute's behavior be changed so that, if a handler does not return a
message, droute will now assume that the handler already sent a reply,
rather than synthesizing a default empty reply. Thus, handlers are now
required to return a value DBusMessage.
Perhaps the API should really be asynchronous, with a callback to be
invoked when the action finishes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
If we don't have a valid object path in emit_event (ie, if NULL is
passed in, for some strange reason), then return rather than crashing in
libdbus.
https://bugzilla.gnome.org/show_bug.cgi?id=669794
|
| | |
|
| | |
|
| |
|
|
|
|
| |
If atk_object_ref_state_set returns NULL, then perhaps the object is
going away or not yet initialized, so caching it may not be a good idea.
Also stops some warnings.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Items are added to the cache in an idle (see commit 75ff19), meaning
that it is possible for an object to go away between the time it is
queued for addition and the time the additions are made.
https://bugzilla.gnome.org/show_bug.cgi?id=666371
|
| |
|
|
|
|
| |
Change schema path from /a11y/ to /org/a11y/.
https://bugzilla.gnome.org/show_bug.cgi?id=663967
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There are a few places where the glib list apis
aren't being used right:
1) There is code that use GList functions on GSLists
2) There is code that uses the list node itself instead
of the node data
3) There is code that removes nodes from a list as its iterating
over that list.
https://bugzilla.gnome.org/show_bug.cgi?id=659967
|
| |
|
|
|
|
| |
It doesn't make sense to expose atk_object_set_name and
atk_object_set_description over D-Bus. Removing the ability to set those
properties.
|
| | |
|
| |
|
|
|
|
|
|
| |
Fetch a list of active keystroke and mouse event listeners, and monitor
for changes. Enable event watching if keyboard listeners are present.
This requires the newest revision of at-spi2-core.
Fixes http://bugzilla.gnome.org/show_bug.cgi?id=666870
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We don't want to deregister them when they are changing from defunct to
functioning. And GTK 3.4 emits that change after setting up the
accessible.
|
| |
|
|
|
|
|
| |
at-spi2-core now uses arg0path to create match rules to catch events
with suffixes (ie, :system), but this is kind of stretching the intended
purpose of arg*path, which expects paths delimited with /'s, so replace
a : with a /. The / is changed back to a : in at-spi2-core.
|
| | |
|
| |
|
|
|
|
|
| |
It is dangerous to unref cache objects inside a g_hash_table_foreach,
since, if the object is finalized, it will be removed, which can cause
problems with the iterator. Instead, make a GSList of the objects to
unref, then use this GSList to unref.
|
| |
|
|
|
|
|
|
|
| |
It is possible, at least in theory, that querying one accessible could
have the side effect of another accessible being dereferenced. If this
results in the accessible being finalized, then this would likely cause
a crash when potentially iterating over the newly-finalized object.
Hopefully fixes http://bugzilla.gnome.org/show_bug.cgi?id=664822
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
It should be enough to retrieve some info about the children, in the
socket adaptor's handler for the "Embedded" D-Bus method. Asking for
the number of the plug's children seems to be a good candidate.
https://bugzilla.gnome.org/show_bug.cgi?id=663876
|
| |
|
|
|
|
|
|
|
|
| |
Calls to atk_object_ref_state_set() are expected to return a valid
state set always, so it would be better if this implementation of
socket's ref_state_set() returned empty sets instead of just NULL, to
avoid calling to atk_state_set_*() functions over invalid instances of
AtkStateSet (e.g. add_pending_items() in accessible-cache.c).
https://bugs.freedesktop.org/show_bug.cgi?id=42350
|
| | |
|
| |
|
|
|
|
|
|
| |
spi_dbus_message_iter_append_struct has an early exit where it
forgets to call va_end(). Harmless most of the time, but it
upsets static analyzers.
https://bugzilla.gnome.org/show_bug.cgi?id=662248
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The workaround that was committed for this didn't have the
intended effect, since the timeout was added to the default
main context, not the one that is used in the recursive
mainloop.
Without this patch, my login screen would freeze when hitting
Enter in the password entry, with it, I could successfully log
in 10 out of 10 times.
https://bugzilla.gnome.org/show_bug.cgi?id=658013
|
| | |
|
| |
|
|
|
|
|
| |
For some reason, if the dbus connection goes away during a call to
NotifyListenersSync, the DBusPendingCall is not notified. This may be a
libdbus bug. Working around the issue by adding a timeout that will
check for a disconnect and abort the call as needed.
|
| | |
|
| | |
|
| | |
|
