Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-97185

Quick DragHandler Reporting Wrong Coordinates using TouchScreen Input

    XMLWordPrintable

Details

    • Windows
    • d08038ba70 (qt/qtdeclarative/dev) d08038ba70 (qt/tqtc-qtdeclarative/dev) ee68d19b1d (qt/qtdeclarative/6.3) ee68d19b1d (qt/tqtc-qtdeclarative/6.3) cf39c6e28d (qt/qtdeclarative/6.2) cf39c6e28d (qt/tqtc-qtdeclarative/6.2) cf39c6e28d (qt/qtdeclarative/6.2.4)

    Description

      In the following code, figure dragging reports wrong x and y coordinate values when display scaling is set to something else than 100%. 

      import QtQuick
import QtQuick.Window

Window {
    width: 600
    height: 600
    visible: true
    
Rectangle 
   {
       x: 300
       y: 300
       color: "red"
       radius: 50
       width: 30
       height: 30
   }

    Text {
        text: handler.centroid.position.x.toFixed(1) + "," + handler.centroid.position.y.toFixed(1)
    }

    DragHandler {
        id: handler
        target:null
    }
}

      How to reproduce
      1. Set screen scaling to e.g. 200%
      2. Use QTBUG97185.zip
      3. Touch the red circle -> This outputs around 300, 300
      4. Drag towards the red circle -> This outputs e.g. 542, 553 as if it's dragging towards x:600 y:600

      What is known

      • Not reproducible in Qt5.12 and Qt5.15
      • Mouse dragging works fine
      • Touching and untouching produces correct coordinate values

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-98486 Touch points coordinates does not take into account the Device Pixel Ratio on Windows

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-98543 Invalid updates of contentY of Flickable on touch screen

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97157 attempting to interact with any widget dialog on touchscreen fails; mouse causes crash after that

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              srutledg Shawn Rutledge
              nagrohn Nahomi Gröhn (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews