AutoInput Click works right, Long Click work wrong.

Discussion in 'AutoApps' started by Steve Hogan, May 15, 2020.

  1. Steve Hogan

    Steve Hogan New Member

    Joined:
    May 15, 2020
    Messages:
    2
    Likes Received:
    0
    I have a simple task that answers the phone, selects the keypad, pushes the 9 key and then drops the call.
    Here is the relevant portion of the task:

    A15: Take Call
    A16: Wait [ MS:750 Seconds:0 Minutes:0 Hours:0 Days:0 ]
    A17: AutoInput Action [ Configuration:Type: Text
    Value: Keypad
    Action : Click Timeout (Seconds):20 ]
    A18: Wait [ MS:750 Seconds:0 Minutes:0 Hours:0 Days:0 ]
    A19: AutoInput Action [ Configuration:Type: Text
    Value: 9
    Action : Click Timeout (Seconds):20 Continue Task After Error:On ]
    A20: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
    A21: End Call

    When A19 Action = Click, everything works fine. When A19 action = Long Click, it hits the 8 key instead of the 9 key. I've tried Nearby Text using wxyz (which is on the same keytop) to see if this helps but no success. I would really like to use the Long Click as the DTMF receiver on the other end is somewhat marginal with the standard length tone. Thoughts?
     
  2. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,236
    Likes Received:
    777
    Unfortunately some times some apps don't respond well to accessibility service long click commands like that, sorry! Maybe you can try using the AutoInput Gestures action instead to do the long click? :)
     
  3. Steve Hogan

    Steve Hogan New Member

    Joined:
    May 15, 2020
    Messages:
    2
    Likes Received:
    0
    Thanks for looking at this.

    The issue isn't that the app is not responding. It responds in both cases. I'm just trying to generate a long click on the same button as the short click. When I use AutoInput with Action = Click, everything is fine. It clicks the 9 key no problem. When I change the Action to Long Click, it clicks the 8 key instead of the 9 key. Nothing else is changed. I would expect that the code to locate the input field is the same in both cases.

    I will look at Gestures and see if that can be utilized.
     

Share This Page