Re: [g-a-devel] How to choose the suitable event in AT-SPI





On Fri, Dec 5, 2014 at 4:43 AM, Michael Pozhidaev <msp altlinux ru> wrote:
Hello all,

I got a question regarding choosing the most relevant event for the
particular user action. When the user does something (presses the key or
anything else) his/her action usually yields the several events which go
through registryd and are transmitted to AT. The problem is how to
choose among them the most preferable one? We can collect them and do
the selection but for that we should be sure that know them all and for
the last user action there will no events any more. This require a some
sort of transactions or packets and I am wondering is there any way to
ensure that we got everything for the last user action? Maybe my
approach is wrong and I would be thankful if somebody can help me to
understand what I should do with that.

What is it you mean by "most preferable event"? Can you clarify that a bit further?

I wonder whether it would be beneficial to you if you were to have a play about with some simple at-spi2 examples. If you like you can file a bug to request an example to demonstrate some aspect of events which you would like to understand better. Take a look at Alejandro's examples  github repository in if that seems like it might be useful:  https://github.com/infapi00/at-spi2-examples

Speaking "the most preferable event" I mean the most relevant event to
construct a user feedback. For example, when the user presses keys in
the editable text, the events reflecting caret move and text changing arrive.
Among them we need the text changing one while caret move is very
confusing because it could be caused just by pressing the arrows.

You mean hitting the arrow keys to might the cursor? In that case then the caret has moved so it is correct to say this event is a caret-moved one. Or do you mean to say that in some instances the caret is not moving and these events are still firing out regardless?

Magdalen



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]