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

194 lines
9.6 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.Event.Object">
<signal name="PropertyChange"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="BoundsChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="LinkSelected"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="StateChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ChildrenChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="VisibleDataChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="SelectionChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ModelChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ActiveDescendantChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="RowInserted"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="RowReordered"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="RowDeleted"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ColumnInserted"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ColumnReordered"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ColumnDeleted"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="TextBoundsChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="TextSelectionChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="TextChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="TextAttributesChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="TextCaretMoved"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="AttributesChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Window">
<signal name="PropertyChange"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Minimize"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Maximize"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Restore"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Close"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Create"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Reparent"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="DesktopCreate"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="DesktopDestroy"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Destroy"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Activate"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Deactivate"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Raise"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Lower"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Move"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Resize"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Shade"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="uUshade"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Restyle"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Mouse">
<signal name="Abs"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Rel"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Button"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Keyboard">
<signal name="Modifiers"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Terminal">
<signal name="LineChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ColumncountChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="LinecountChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ApplicationChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="CharwidthChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Document">
<signal name="LoadComplete"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="Reload"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="LoadStopped"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="ContentChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="AttributesChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
<signal name="PageChanged"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
<interface name="org.a11y.atspi.Event.Focus">
<signal name="Focus"><arg direction="in" type="(suuv)"/>
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="QSpiEvent"/>
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
</signal>
</interface>
</node>
Reference in New Issue Copy Permalink