Skip to content
Snippets Groups Projects
  1. Apr 24, 2018
  2. Apr 21, 2018
  3. Apr 16, 2018
  4. Mar 27, 2018
  5. Mar 26, 2018
  6. Mar 23, 2018
  7. Mar 21, 2018
  8. Mar 20, 2018
  9. Mar 18, 2018
  10. Mar 15, 2018
  11. Mar 13, 2018
  12. Mar 12, 2018
  13. Mar 09, 2018
  14. Mar 08, 2018
  15. Mar 07, 2018
  16. Mar 05, 2018
  17. Mar 01, 2018
  18. Feb 28, 2018
  19. Feb 27, 2018
    • Johan Klokkhammer Helsing's avatar
      Init variables where they are declared when possible (clang-tidy) · c4bd9198
      Johan Klokkhammer Helsing authored
      
      clang-tidy -p compile_commands.json $file \
          -checks='-*,modernize-use-default-member-init,readability-redundant-member-init' \
          -config='{CheckOptions: [{key: modernize-use-default-member-init.UseAssignment, value: "1"}]}' \
          -header-filter='qtwayland' \
          -fix
      
      Afterwards I ran search and replace on the diff to clean up some whitespace errors:
      
      - Replaced '(\n\+[^:\n]*)(:\s+\+\s+)' with '$1: '
      - Replaced '(\n\+[^,\n]*)(,\s+\+\s+)' with '$1, '
      - Replaced '\n\+\s*\n' with '\n'
      
      I also had to do some manual edits, because for some reason, this particular
      clang-tidy check doesn't trigger for some files.
      
      Change-Id: I3b3909bac4bf20108bbe8ad1e01bcc54236dae1b
      Reviewed-by: default avatarShawn Rutledge <shawn.rutledge@qt.io>
      c4bd9198
  20. Feb 26, 2018
  21. Feb 21, 2018
    • Kari Oikarinen's avatar
      Fix use after free in tst_WaylandClient::dontCrashOnMultipleCommits · ec495c98
      Kari Oikarinen authored
      
      QBackingStore had a pointer to TestWindow window, but it was destroyed only
      after the TestWindow was already deleted.
      
      Change-Id: Id8fe38277cf843d532f2d8c2fdbe1f69d0309a7f
      Reviewed-by: default avatarJohan Helsing <johan.helsing@qt.io>
      v5.11.0-beta1
      ec495c98
    • Johan Klokkhammer Helsing's avatar
      Fix crash when connecting a new screen · fd9fec4f
      Johan Klokkhammer Helsing authored
      
      In QWaylandWindow::virtualSiblings, don't include screens that have not been
      added yet. I.e. QWaylandScreens for which QPlatformIntegration::screenAdded has
      not yet been called.
      
      There are two reasons why this crash wasn't covered by the
      removePrimaryScreen() test. First of all, the mock output didn't send
      wl_output.done events when updating the mode/geometry. These wayland events are
      what causes QWindowSystemInterface::handleScreenGeometryChange() to be called
      (where virtualSiblings are called).
      
      Furthermore, virtualSiblings is only called when the geometry actually changes,
      so add a new test that changes the screen geometry of the existing screen while
      a new one is being added (i.e. moves it to the right).
      
      Task-number: QTBUG-62044
      Change-Id: I623fbf8799d21c6b9293e7120ded301277639cc6
      Reviewed-by: default avatarDavid Edmundson <davidedmundson@kde.org>
      Reviewed-by: Aleix Pol
      Reviewed-by: default avatarPaul Olav Tvete <paul.tvete@qt.io>
      fd9fec4f
    • Johan Klokkhammer Helsing's avatar
      Fix flakiness in tst_WaylandClient::events · 3dd9c91b
      Johan Klokkhammer Helsing authored
      
      The test was flaky because we have a workaround for a bug in Weston where
      Weston fails to send the last wl_touch.frame event (QTBUG-36602). We've worked
      around it by letting our client handle the wl_touch.up event before the frame
      event if it's the last up event.
      
      This caused a race condition in our tests, though (which include the frame
      event). Because Q_TRY_COMPARE(window.touchEventCount, 1) would pass and the
      window was sometimes destroyed before the frame event had been sent by the
      compositor thread.
      
      Work around it by moving the touch testing before the pointer testing, so the
      surface is still alive when the compositor tries to send the frame event. That
      way the test will not be flaky, and will continue to work when we eventually
      remove the workaround in QWaylandInputDevice.
      
      Task-number: QTBUG-66537
      Change-Id: I5673445682810e75343c6df2d1b2a4f1c1b21bcb
      Reviewed-by: default avatarPaul Olav Tvete <paul.tvete@qt.io>
      3dd9c91b
  22. Feb 20, 2018
  23. Feb 18, 2018