AutoInput Questions

[Mike Wilson]

I'm trying to do a couple of different things with AutoInput and it doesn't seem to be behaving as I thought it would.

1) I'm trying to click on a menu in an app that only shows up once the main screen is tapped.  The AutoInput popup that appears in the status bar after selecting the app screen says to select an element with "a single long-touch" on the element.  However, as soon as I touch anything, it assumes that's the element I want.  In other words, it's reacting to a short touch rather than waiting for a long one.  So, in this case, I can't touch the screen to bring up the menu. Any workaround for that?

2) The timeout function doesn't seem to...function.  I was under the impression that the timeout was the period during which AutoInput would wait until discarding the action. Is that correct?  In my particular case, I'm trying to click on the Google Maps popup that asks me if I want screen dimming or not.  I was able to select it when I set up the action, but in reality it can take several seconds before it appears on the screen.  I thought that by setting a timeout high enough, AutoInput would wait until it saw that popup and then execute the action, but it seems that unless the box is already showing, the action is discarded. Am I just misunderstanding what the timeout value is?

Thanks for your help.

[João Dias]

Hi. Thanks for your questions :)

1) You should only "long-touch" the element you want AutoInput to click when it's already showing on the screen :) I used the term "long-touch" because on some elements that's what's needed for it to register and on all others it will also work. In short, make sure the element you want to click is visible on the screen before selecting it.

2) yes, that's what the timeout is for. Take care that the Tasker Timeout itself is also set to a high-enough value.

Hope this helps.

--
You received this message because you are subscribed to the Google Groups "joaomgcd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joaomgcd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mike Wilson]

Thanks for getting back to me.

Unfortunately, I can't get the element that I really want to click to appear on the screen without first touching the screen; it's a popout menu that only appears after a screen touch.  I may be out of luck with that one.

Can you clarify what you mean by Tasker's timeout?  The only timeout setting I see is the one on the plugin configuration screen (Tasker's usual one that it uses for all plugins.)  Is there a second one?

Thanks for your help.

[João Dias]

Hi again.

You should touch the item that makes  the popup menu appear and only then capture the element you want to click :)

There are 2 timeouts. The one you configure in Tasker and another one in the AutoInput action itself. You should change both to the value of your liking. I have asked Tasker's developer to provide Tasker's timeout value to plugins so that users don't have to configure this twice, but for now this is how it has to be, sorry :)

--

[Mike Wilson]

Sorry to be so dense...

I've given up on the first one because I don't think it can be done; as soon as I touch the screen to get the menu I need, AutoInput assumes that the element I want when it's really the one that appears after the touch.  At any rate, it's just an icon that I'm trying to hit; no text, so I don't think it will work in any case.

As for the timeout, I've attached a screenshot of the only one I see, but it sounds like there's another one.  I can't find it, though.  Any help appreciated.

[João Dias]

Can't you do this?

- start the Easy setup process, but don't press the "Add" button

- touch the screen to get to the menu you want

- press the "Add" button

- touch the item inside the menu

What part of this doesn't work?

About the timeout, it's inside the actual "AutoInput Action" settings, under Advanced :)

[Mike Wilson]

Thanks for your help and patience.

For the tapping problem, I think it may just be the app itself (GPS Status).  The icons on the menu don't seem to be visible to AutoInput.  Not a big deal at this point.

Thanks for pointing out where to find the timeout setting.  I'll give that a shot.

Again, I appreciate the support you provide. 

[João Dias]

Can you please link me to that app? :) I'd be curious to try it out myself.

--

[Mike Wilson]

Sure.  Here it is:

https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2

[Mike Wilson]

I should have mentioned that what I was really trying to do is to automate downloading new A-GPS data, which requires a screen touch to get to the menu, a touch on the wrench icon, choosing "Manage A-GPS State", and then tapping "Download".

[Mike Wilson]

[Mike Wilson]

[João Dias]

I managed to do it :)

Check out this task I exported: https://drive.google.com/file/d/0B8G77eDgeMdwNGJwc3M2S0dVems/edit?usp=sharing

Hope this helps :)

On Wed, Sep 24, 2014 at 2:21 PM, Mike Wilson <micha...@gmail.com> wrote:

I should have mentioned that what I was really trying to do is to automate downloading new A-GPS data, which requires a screen touch to get to the menu, a touch on the wrench icon, choosing "Manage A-GPS State", and then tapping "Download".

--

[Mike Wilson]

Excellent!  Thank you very much!

I wasn't able to import the task.  It just came in with the title and no actions in Tasker and I couldn't figure out how to do it in AutoInput, but I was able to look at the xml and figured out what I need to enter manually to make my own version work.  And, of course, after I did that, I was finally able to do it via clicking.  Just knowing that it could be done was a big help.

You make great apps and provide great support.  Well done.

[João Dias]

Great that you got it working! :) Don't forget to rate the app on Google Play if you like it ;) 

Thanks!