AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
9356dfc404
gtk2/gtk/a11y/atspi/DeviceEventController.xml

61 lines
2.2 KiB
XML
Raw Normal View History

a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<node name="/node">
<interface name="org.a11y.atspi.DeviceEventController">
<method name="RegisterKeystrokeListener">
<arg direction="in" name="listener" type="o"/>
a11y: Resync the AT-SPI XML Mostly just changes in the annotations coming from at-spi2-core, but it's good to try and keep the XML in sync.
2020-11-12 23:26:03 +00:00
<arg direction="in" name="keys" type="a(iisi)"/>
<annotation name="org.qtproject.QtDBus.QtTypeName.In1" value="QSpiKeyTypeArray"/>
a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
<arg direction="in" name="mask" type="u"/>
a11y: Resync the AT-SPI XML Mostly just changes in the annotations coming from at-spi2-core, but it's good to try and keep the XML in sync.
2020-11-12 23:26:03 +00:00
<arg direction="in" name="type" type="au"/>
<annotation name="org.qtproject.QtDBus.QtTypeName.In3" value="QSpiEventTypeArray"/>
<arg direction="in" name="mode" type="(bbb)"/>
<annotation name="org.qtproject.QtDBus.QtTypeName.In4" value="QSpiEventMode"/>
a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
<arg direction="out" type="b"/>
</method>
<method name="DeregisterKeystrokeListener">
<arg direction="in" name="listener" type="o"/>
a11y: Resync the AT-SPI XML Mostly just changes in the annotations coming from at-spi2-core, but it's good to try and keep the XML in sync.
2020-11-12 23:26:03 +00:00
<arg direction="in" name="keys" type="a(iisi)"/>
<annotation name="org.qtproject.QtDBus.QtTypeName.In1" value="QSpiKeyTypeArray"/>
a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
<arg direction="in" name="mask" type="u"/>
<arg direction="in" name="type" type="u"/>
</method>
<method name="RegisterDeviceEventListener">
<arg direction="in" name="listener" type="o"/>
<arg direction="in" name="types" type="u"/>
<arg direction="out" type="b"/>
</method>
<method name="DeregisterDeviceEventListener">
<arg direction="in" name="listener" type="o"/>
<arg direction="in" name="types" type="u"/>
</method>
<method name="GenerateKeyboardEvent">
<arg direction="in" name="keycode" type="i"/>
<arg direction="in" name="keystring" type="s"/>
<arg direction="in" name="type" type="u"/>
</method>
<method name="GenerateMouseEvent">
<arg direction="in" name="x" type="i"/>
<arg direction="in" name="y" type="i"/>
<arg direction="in" name="eventName" type="s"/>
</method>
<method name="NotifyListenersSync">
<arg direction="in" name="event" type="(uiuuisb)"/>
<arg direction="out" type="b"/>
a11y: Resync the AT-SPI XML Mostly just changes in the annotations coming from at-spi2-core, but it's good to try and keep the XML in sync.
2020-11-12 23:26:03 +00:00
<annotation name="org.qtproject.QtDBus.QtTypeName.In0" value="QSpiDeviceEvent"/>
a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
</method>
<method name="NotifyListenersAsync">
<arg direction="in" name="event" type="(uiuuisb)"/>
a11y: Resync the AT-SPI XML Mostly just changes in the annotations coming from at-spi2-core, but it's good to try and keep the XML in sync.
2020-11-12 23:26:03 +00:00
<annotation name="org.qtproject.QtDBus.QtTypeName.In0" value="QSpiDeviceEvent"/>
a11y: Add the AT-SPI DBus descriptions And generate the code for the DBus interfaces. We don't want the full object manager experience, here, because we're going to have a single object responding to various interfaces and remote method calls. For this reason, we're not using the gnome module in Meson to call gdbus-codegen for us: we need to use the interface info command line arguments, and those are not available from Meson.
2020-09-29 16:55:01 +00:00
</method>
</interface>
</node>
Reference in New Issue Copy Permalink