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

Windows messages sent twice to event filters, WM_CHAR missing completely

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P4: Low
    • 5.11.1
    • 5.10.1
    • QPA: Windows
    • None
    • Windows 10 64-bit

      Visual Studio 2015 Update 3

      Qt 5.10.1
    • a0a22037cdacbf51a2db560ff902a5a341561b15 (qtbase/5.11. 23.4.2018,5.11)

    Description

      When registering native event filters on Windows - each mouse and keyboard event is duplicated. Othe the other hand, some events like WM_CHAR are "swallowed". I see the following output in logging for every event (left mouse button clicked, then one character typed):

      WM_LBUTTONDOWN
      WM_LBUTTONDOWN
      WM_LBUTTONUP
      WM_LBUTTONUP
      WM_KEYDOWN
      WM_KEYDOWN
      WM_KEYUP
      WM_KEYUP

       

      While plain C WinAPI message loop logging results in:

      WM_LBUTTONDOWN
      WM_LBUTTONUP
      WM_KEYDOWN
      WM_CHAR
      WM_KEYUP

       

       

      The test project (find attached) is a basic QML project using Visual Studio 2015 32-bit for building. It creates single blank ApplicationWindow and registers object of class inheriting from QAbstractNativeEventFilter using QApplication::installNativeEventFilter.

      The issue is serious since we have some 3rd party components that depend on correct handling of native windows events and the current message loop seems messed up...

      Attachments

        1. TestMessaging.zip
          4 kB
        2. qtbug67095.zip
          3 kB
        3. qtbug67095_widgets.zip
          2 kB
        4. qtbug67095_log.txt
          111 kB
        5. qtbug67095_diag2.diff
          4 kB
        6. qtbug67095_diag.diff
          3 kB
        7. output.txt
          0.5 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-42183 QWidget::nativeEvents doesn't receive WM_KEY* messages

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-69687 Running an event loop with ExcludeUserInputEvents still passes input events to QWidget::nativeEvent() instead of queueing as in Qt 4

          • 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-69074 The implemented nativeEvent message is not match as sent

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              kleint Friedemann Kleint
              r0ll1ngst0ne Michael Kostukov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes