gtk4 a11y: Implement new GtkAccessibleTextInterface::get_offset

Implement the new `get_offset` method for
`GtkAccessibleTextInterface` newly introduced
in GTK 4 in GTK commits

commit f802be88e98f817c3d6fa048bf79d82de60173d3
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sun Mar 10 10:27:56 2024 -0400

a11y: Use gtk_accessible_text_get_offset

Implement GetOffsetAtPoint using gtk_accessible_text_get_offset.

commit b9d2049991427e8dee443e9f3b683e52c96d6b83
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sun Mar 10 10:27:32 2024 -0400

a11y: Add gtk_accessible_text_get_offset

This is not implemented yet.

commit cfe35586107d7c42eb3af7aa38ee23df22f718d0
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sun Mar 10 10:02:24 2024 -0400

a11y: Add GetOffsetAtPoint

We don't handle it yet.

In order for this to actually work on the AT-SPI level,
this also needs fixes on the GTK side. Pending MR: [1]

With this, the previous

Change-Id: I7d171b6696037a696f0d767d3134c7a7184f93a3
Author: Michael Weghorn <m.weghorn@posteo.de>
Date:   Thu Apr 4 11:08:10 2024 +0200

gtk4 a11y: Implement new GtkAccessibleTextInterface::get_extents

and the mentioned GTK MR in place, a quick test with a Writer
paragraph using Accerciser's IPython console now looks OK:

In [1]: acc.queryText().getCharacterExtents(5, pyatspi.XY_WINDOW)
Out[1]: (483, 219, 4, 18)
In [2]: acc.queryText().getOffsetAtPoint(484, 220, pyatspi.XY_WINDOW)
Out[2]: 5

[1] https://docs.gtk.org/atk/vfunc.Text.get_range_extents.html

Change-Id: Ieb45e3d0d6f37350898ffee081491bf94b6dbea0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165794
Tested-by: Jenkins
Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>

0 files changed, 0 insertions, 0 deletions