1

Feature Request: AutoInput v2

In AutoInput v2, there is a "Wait For Element" action that waits until an element appears on the screen.

My current AutoInput workflow is like this:

click(id, %button_id) --> waitForElement(id, %loader_id) --> click(id, %button_id)

Since the loader's element ID is often hard to get (as it disappears instantly due to fast loading), could you add a "Wait For Element to Disappear" action that waits for an element to disappear?

This way, the workflow would only depend on %button_id and would become like this:

click(id, %button_id) --> waitForElementDisappear(id, %button_id) --> click(id, %button_id)

*Note: The loader element makes the button disappear from the screen temporarily.

Follow

1 reply

Votes Newest Oldest
S

To clarify, I think you're asking for the workflow to look like this - 

`click(id, %button_id)` -> `WaitForElementToDisappear(id, %button_id)` -> `WaitForElement(id, %button_id)` -> `click(id, %button_id)`

You'd need to wait for it to disappear, then wait for it to _appear_ again. I'm not sure how the `WaitForElement` feature is implemented in Tasker but I _imagine_ it would be doable. 

That said, I think it's enough of an edge-case it probably won't get implemented any time soon. You can pretty much always just use the `wait` action for about a hundred milliseconds then do the `WaitForElement(id, %button_loader)` call, or wait for some element on-screen that will be updated to some new value after the loading is done and wait for _that_ to change. 

Comment
Reply