[BRLTTY] Routing key events

[payman shaykhmehdi]

>
> if you could be more precise as to what you want to achieve in the end,
> we might suggest a way to achieve it


I'm developing an application in QT framework. In this application I have a
textedit widget (QTextEdit). I was expecting that by default pressing a
routing key moves the text cursor to the specific character under the
routing key in the textedit.
But that is not happening, So I'm trying to somehow grab the routing key
and move the text cursor to the relevant position.

Currently I'm using the eventFilter() function of QObject and I've
discovered that by pressing a routing key, a QPaintEvent received by qt
textedit object. But this event gives me a graphical region and, by this
region information, I can't route the text cursor to the specific character
determined by the routing key.

Is it possible to use Orca scripting capabilities to achieve this?


On Thu, Aug 29, 2019 at 1:47 PM Samuel Thibault <
samuel.thibault at ens-lyon.org> wrote:

> payman shaykhmehdi, le jeu. 29 août 2019 13:30:08 +0430, a ecrit:
> > But the point is that I don't want to use brlapi in my application,
>
> Ah
>
> > I'm trying to grab the system event that a routing key triggers.
>
> There is no system equivalent to a routing key.
>
> The routing keys are tighly coupled to what is being displayed on the
> braille output, which is not managed by the system, but by orca.
>
> What would thus happen is that orca catches the event through brlapi,
> and e.g. call atspi_text_set_caret_offset, which will be directly fed to
> the application toolkit's widget.
>
> If you could be more precise as to what you want to achieve in the end,
> we might suggest a way to achieve it (http://xyproblem.info/).
>
> Samuel
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20190829/555750a6/attachment.html>