Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. TapHandler on android getting time held
Qt 6.11 is out! See what's new in the release blog

TapHandler on android getting time held

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
3 Posts 1 Posters 388 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Vega4
    wrote on last edited by Vega4
    #1

    Arlight, the value timeHeld when checked within onLongPressed seems to always be a random value less than 1 ideas?

    Also, when checking point.timeHeld onGrabChanged it always returns 0

    Update: couldn't get time from timeHeld so implemented our own timer on the backend side and are executing its subroutines from QML when needed (it's a real pity).

    Now, another problem, when user holds Tap-Area for few seconds onGrabChanged is not fired at all, instead.. 'onTapped' fires; what's going on here? Tried changing policies ->it's the same.

    On Android scenario:

    1. user taps -> long press is fired after some time
      now, we're after getting for how long it was pressed
      and now
    2. onGrabChanged would never fire if held for few seconds, instead
      3)onTapped fires AND the timeHeld within the event point param is ALWAYS 0.
    V 2 Replies Last reply
    0
    • V Vega4

      Arlight, the value timeHeld when checked within onLongPressed seems to always be a random value less than 1 ideas?

      Also, when checking point.timeHeld onGrabChanged it always returns 0

      Update: couldn't get time from timeHeld so implemented our own timer on the backend side and are executing its subroutines from QML when needed (it's a real pity).

      Now, another problem, when user holds Tap-Area for few seconds onGrabChanged is not fired at all, instead.. 'onTapped' fires; what's going on here? Tried changing policies ->it's the same.

      On Android scenario:

      1. user taps -> long press is fired after some time
        now, we're after getting for how long it was pressed
        and now
      2. onGrabChanged would never fire if held for few seconds, instead
        3)onTapped fires AND the timeHeld within the event point param is ALWAYS 0.
      V Offline
      V Offline
      Vega4
      wrote on last edited by
      #2
      This post is deleted!
      1 Reply Last reply
      0
      • V Vega4

        Arlight, the value timeHeld when checked within onLongPressed seems to always be a random value less than 1 ideas?

        Also, when checking point.timeHeld onGrabChanged it always returns 0

        Update: couldn't get time from timeHeld so implemented our own timer on the backend side and are executing its subroutines from QML when needed (it's a real pity).

        Now, another problem, when user holds Tap-Area for few seconds onGrabChanged is not fired at all, instead.. 'onTapped' fires; what's going on here? Tried changing policies ->it's the same.

        On Android scenario:

        1. user taps -> long press is fired after some time
          now, we're after getting for how long it was pressed
          and now
        2. onGrabChanged would never fire if held for few seconds, instead
          3)onTapped fires AND the timeHeld within the event point param is ALWAYS 0.
        V Offline
        V Offline
        Vega4
        wrote on last edited by Vega4
        #3

        Qeustion is : how to properly access timeHeld during a long-press/hold from QML

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved