From 8ac74a0842310acd8bc0fc12bccc66a49ce1f922 Mon Sep 17 00:00:00 2001 From: Mike Gorse Date: Tue, 28 Mar 2023 13:10:18 -0500 Subject: Add some notes for possible future API-breaking changes --- devel-docs/at-spi3.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/devel-docs/at-spi3.rst b/devel-docs/at-spi3.rst index 3e504cf4..1505fa24 100644 --- a/devel-docs/at-spi3.rst +++ b/devel-docs/at-spi3.rst @@ -28,6 +28,14 @@ future version of the API. 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. + semantics of their type sent over DBus. + +- ChildCount and GetChildAtIndex could have unsigned arguments (#106). + +- For the Collection interface, roles are signed, but they are unsigned + elsewhere (#108). + +- For the Collection interface, states are signed, but they are unsigned + elsewhere (#109). - The AtspiEventListener API is hard to use and also needs to be reworked. -- cgit v1.2.1