Autoinput UI update interval

[Ed Newman]

Is there a setting somewhere to set the interval autoinput uses to check for a change on the screen to trigger a profile, event, plugin, autoinput, ui update?

There seems to be about 1 second delay from when text appears on the screen until the first line in the task tied to the profile runs.
I put an alert, beep as the first line to test it.

I need it much shorter.

Thanks.

[Ed Newman]

Guess not!

[Robert Ryan]

The delay is caused by Android's accessibility service and is outside of Tasker's control. Tasker responds as soon as it receives the message from the service. 

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/73c47493-e4fe-46fb-b3f8-fbb77ccd9d4a%40googlegroups.com.

[Ed Newman]

It's much faster if I just query the screen myself using autoinput ui query.

Doesn't that use the same accessibility service?

The problem with me querying it is I can't query it until the previous command, an autoinput swipe gesture is complete

where I was hoping the ui update would respond immediately to a screen update.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/170a6c6cf60.2819.558997d9ea49a12c5d90790601ab7599%40gmail.com.

[Robert Ryan]

On March 4, 2020 11:28:47 AM Ed Newman <ed0...@gmail.com> wrote:

It's much faster if I just query the screen myself using autoinput ui query.

Doesn't that use the same accessibility service?

Yes, but using two different methods. 

The UI Update event installs an asynchronous listener that waits for messages from the service.

The UI Query action is a one time demand for information.