Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. qt.pointer.dispatch touch errors
Forum Updated to NodeBB v4.3 + New Features

qt.pointer.dispatch touch errors

Scheduled Pinned Locked Moved Unsolved General and Desktop
4 Posts 3 Posters 1.8k 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.
  • S Offline
    S Offline
    syr123
    wrote on 25 Jun 2022, 01:09 last edited by syr123
    #1

    Hi there!

    I've just finally ported my app from Python 2.7 and Pyside2 to Monterey 12.2, Python version: 3.9.5, PySide6 version: 6.3.0

    When I use my Macbook Pro trackpad and hover and and out of a QGraphicsView, which is the child of QWidget, I seemingly spontaneously get these two messages:

    qt.pointer.dispatch: delivering touch release to same window QWindow(0x0) not QWidgetWindow(0x600003f7a7c0, name="ClipManagerUiClassWindow")
    

    and

    qt.pointer.dispatch: skipping QEventPoint(id=1 ts=0 pos=0,0 scn=427.623,393.774 gbl=427.623,393.774 Released ellipse=(1x1 ∡ 0) vel=0,0 press=-427.623,-393.774 last=-427.623,-393.774 Δ 427.623,393.774) : no target window
    

    Sorry I don't have more detail to provide, I'm at a loss for what's causing this. Happy to provide any other context that would help explain what's going on.

    Are there any ways to get more info on what's triggering this for debugging?

    Thanks for any leads!

    1 Reply Last reply
    0
    • S Offline
      S Offline
      SGaist
      Lifetime Qt Champion
      wrote on 25 Jun 2022, 19:01 last edited by
      #2

      Hi,

      Are you able to reproduce that with a minimal script ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • D Offline
        D Offline
        Dennis_Z
        wrote on 27 Jun 2022, 18:56 last edited by
        #3

        Hi,

        today, I've got the same messages as @syr123 when using PySide6 and PyQtGraph to plot some data. The warning messages occur when using the pyqtgraph.PlotWidget. However, they also appear when using QGraphicsView as in the this minimal example:

        from PySide6 import QtWidgets
        
        
        class MainWindow(QtWidgets.QMainWindow):
        
            def __init__(self):
                super().__init__()
        
                self.myPlot = QtWidgets.QGraphicsView()
                self.setCentralWidget(self.myPlot)
        
        
        if __name__ == '__main__':
            app = QtWidgets.QApplication()
            w = MainWindow()
            w.show()
            app.exec()
        

        The app shows an empty graphics view, as expected. Hovering the mouse over the QGraphicsView widget leads repeatedly to the following two messages:

        qt.pointer.dispatch: delivering touch release to same window QWindow(0x0) not QWidgetWindow(0x600000e02ca0, name="MainWindowClassWindow")
        qt.pointer.dispatch: skipping QEventPoint(id=2 ts=0 pos=0,0 scn=494.183,356.313 gbl=494.183,356.313 Released ellipse=(1x1 ∡ 0) vel=0,0 press=-494.183,-356.313 last=-494.183,-356.313 Δ 494.183,356.313) : no target window
        
        qt.pointer.dispatch: delivering touch release to same window QWindow(0x0) not QWidgetWindow(0x600000e02ca0, name="MainWindowClassWindow")
        
        ...
        

        I'm using Python 3.10.5 with PySide6 ver. 6.3.1 on a MacBook Pro 13 2018 with macOS 12.4.

        Unfortunately, I'm just about to switch from using matplotlib to the Qt Framework for plotting data. So, I don't know whether the problem has existed before updating from a previous PyQt and Python version.

        Any help or workaround is highly appreciated. Thanks!

        1 Reply Last reply
        0
        • S Offline
          S Offline
          SGaist
          Lifetime Qt Champion
          wrote on 7 Jul 2022, 06:27 last edited by
          #4

          After testing, it seems to be something new that comes with PySide 6.3.1, 6.3.0 does not trigger this.

          You should check the but report system to see if it's something known, if not please open a new ticket with your example script and the details of your machine.

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          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