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. QMousepress broken?
Qt 6.11 is out! See what's new in the release blog

QMousepress broken?

Scheduled Pinned Locked Moved Mobile and Embedded
2 Posts 1 Posters 1.0k Views 1 Watching
  • 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.
  • R Offline
    R Offline
    redoctober
    wrote on last edited by
    #1

    Hello all,

    Currently, I have some problems with a 'freezing' touchscreen. My application is very simple: a QApplication which opens a QWebview. This app runs on a Angstrom linux device with touchscreen.
    When I load a webpage, I can click and surf around as usual. But when I do really a lot of random presses with multiple fingers for about 2-3 minutes, the QMousePressEvents stop showing up in the eventfilter of my QWebview. However, mousemove events still show up (the cursor can be moved)

    Does anyone have a clue?

    Of course I checked
    -if my touschreen driver isn't broken, but it appears this is not the case. Press and release events still show up.
    $evtest /dev/input/touchscreen0
    @Event: time 1364508847.130126, type 3 (Absolute), code 24 (Pressure), value 255
    Event: time 1364508847.130157, type 3 (Absolute), code 0 (X), value 229
    Event: time 1364508847.130157, type 3 (Absolute), code 1 (Y), value 97
    Event: time 1364508847.130157, type 1 (Key), code 330 (Touch), value 1
    Event: time 1364508847.130157, -------------- Report Sync ------------
    Event: time 1364508847.137908, type 3 (Absolute), code 0 (X), value 226
    Event: time 1364508847.137908, type 3 (Absolute), code 1 (Y), value 95
    Event: time 1364508847.137939, -------------- Report Sync ------------
    Event: time 1364508847.145721, type 3 (Absolute), code 0 (X), value 225
    Event: time 1364508847.145751, type 3 (Absolute), code 1 (Y), value 94
    Event: time 1364508847.145751, -------------- Report Sync ------------
    Event: time 1364508847.153564, type 3 (Absolute), code 0 (X), value 224
    Event: time 1364508847.153564, type 3 (Absolute), code 1 (Y), value 93
    Event: time 1364508847.153594, -------------- Report Sync ------------
    Event: time 1364508847.372100, type 3 (Absolute), code 1 (Y), value 94
    Event: time 1364508847.372100, -------------- Report Sync ------------
    Event: time 1364508847.387939, type 3 (Absolute), code 1 (Y), value 95
    Event: time 1364508847.387969, -------------- Report Sync ------------
    Event: time 1364508847.395629, type 3 (Absolute), code 1 (Y), value 96
    Event: time 1364508847.395660, -------------- Report Sync ------------
    Event: time 1364508847.411407, type 3 (Absolute), code 0 (X), value 225
    Event: time 1364508847.411407, type 3 (Absolute), code 1 (Y), value 97
    Event: time 1364508847.411437, -------------- Report Sync ------------
    Event: time 1364508847.419128, type 3 (Absolute), code 24 (Pressure), value 0
    Event: time 1364508847.419128, type 1 (Key), code 330 (Touch), value 0
    Event: time 1364508847.419128, -------------- Report Sync ------------@
    -If there is no problem with CPU load. This appears to be about 40%, which is a bit higher than usual (25%)

    Does anyone have an idea?

    1 Reply Last reply
    0
    • R Offline
      R Offline
      redoctober
      wrote on last edited by
      #2

      Probably related to https://bugreports.qt-project.org/browse/QTBUG-15280

      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