diff options
author | Mike Gorse <mgorse@suse.com> | 2023-01-23 22:24:39 +0000 |
---|---|---|
committer | Mike Gorse <mgorse@suse.com> | 2023-01-23 22:24:39 +0000 |
commit | f226b4cd1960e93891ea4b7cb94cff8a593e1127 (patch) | |
tree | 8fef96f72a4f4eaad47cd70fe1e6b4e8ce6129b5 | |
parent | 6e223501be381d1ff7e454be9ec09057b1eb7fb1 (diff) | |
parent | 69bd64dd2c7c953cae65deb17e0db760bd995da3 (diff) | |
download | at-spi2-core-f226b4cd1960e93891ea4b7cb94cff8a593e1127.tar.gz |
Merge branch 'add-atspi3-event-examples' into 'main'
Add example of DBus events that may be reworked.
See merge request GNOME/at-spi2-core!123
-rw-r--r-- | devel-docs/at-spi3.rst | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/devel-docs/at-spi3.rst b/devel-docs/at-spi3.rst index c1cf0e97..3e504cf4 100644 --- a/devel-docs/at-spi3.rst +++ b/devel-docs/at-spi3.rst @@ -17,6 +17,17 @@ future version of the API. applications could then respond to, and applications could similarly query consumers for a list of events that they care about. -- The DBus API for sending events should be reviewed. TODO: flesh this out. +- The DBus API for sending events should be reviewed. All events in the + `xml/Event.xml` file return items with the same "siiva{sv}" signature + when it is not necessary. Take for example "StateChanged", which only + uses the first two variables: a string of the state which has been + changed, and a signed integer that may be either 1 or 0 depending on + if the state has been added or removed. For one thing, it is clear that + the second argument for "StateChanged" should be "b" for bool, and + secondly the arguments "iva{sv}" do not seem to be used at all for this + event, and subsequently could be dropped. This is only the example of + one event with issues like this. Nearly every event has a similar case + of some unused fields, or fields that don't *exactly* match the + smenatics of their type sent over DBus. - The AtspiEventListener API is hard to use and also needs to be reworked. |