1. 04 Jun, 2019 12 commits
  2. 21 May, 2019 1 commit
    • Dmitry Kazakov's avatar
      Fix popup palette in WinInk mode · ae31080a
      Dmitry Kazakov authored
      We should eat synthesized events more carefully in the popup
      palette. The events may come either to the triangle widget or
      to its parent widget, depending on the implementaiton. Therefore
      we use a special event filter for that (KisMouseClickEater).
      Ref T10935
  3. 16 May, 2019 2 commits
    • Dmitry Kazakov's avatar
      Add workaround for handling table press correctly in WinInk mode · d684bc55
      Dmitry Kazakov authored
      Original problem: widgets do not get synthesized mouse-down and
      mouse-press events until the stylus is released
      Reason: if the app accepts the event, WndProc should report
      that to the system (by returning true). This is the only way to
      prevent Windows from starting some system-wide gestures, like
      click+hold -> right button click. If we ignore the event, then
      OS postpones all synthesized mouse events until the entire gesture
      is completed.
      The patch implements a "hackish" workaround for the original problem
      by using the following rules:
      1) All tablet-move events are ignored (without synthesized mouse events
         OS doesn't generate any Enter/Leave events)
      2) All not-accepted tablet press- and release-events and also reported as
         ignored (without it D&D doesn't work).
      3) All accepted tablet press- and release-events are reported as "accepted",
         **but** we artificially synthesize mouse events for them.
      TODO: there are still two problems:
      1) Perhaps this synthesizeMouseEvent() is not needed at all. But we should
         first check if Qt relies on these synthesized messages anywhere in the
         code or not.
      2) If we still keep synthesizeMouseEvent(), then it should fetch actual
         tablet buttons from QGuiApplicationPrivate::tabletDevicePoint(). Right
         now it always synthesizes left-click, whatever the button was pressed/
    • Dmitry Kazakov's avatar
      Fix using tablet on QML widgets · 8dd4d8b9
      Dmitry Kazakov authored
      In previous versions of Qt (wintab impeplementation) the events were
      marked by Qt::MouseEventSynthesizedBySystem flag only when they were
      synthesized from touch, not from tablet events. This is what
      QWindowsTabletSupport does and what QQuickWindow expects (it
      filters out all synthesized events). This patch recovers the old behavior
      for the new QWindowsPointerHandler tablet API implementation.
  4. 09 May, 2019 1 commit
  5. 07 May, 2019 1 commit
  6. 25 Apr, 2019 2 commits
  7. 23 Apr, 2019 2 commits
  8. 22 Apr, 2019 2 commits
  9. 19 Apr, 2019 2 commits
  10. 18 Apr, 2019 4 commits
  11. 17 Apr, 2019 1 commit
    • Dmitry Kazakov's avatar
      Switch stylus pointer type when the tablet is in the tablet proximity · 714c9aae
      Dmitry Kazakov authored
      Some convertible tablet devices have a special stylus button that
      converts the stylus into an eraser. Such button can be pressed right
      when the stylus is in tablet surface proximity, so we should check
      that not only during proximity event handling, but also while parsing
      normal wintab packets.
  12. 16 Apr, 2019 2 commits
    • Dmitry Kazakov's avatar
      Fix setting custom tablet mapping · 9cf5c866
      Dmitry Kazakov authored
      1) Fix support for negative offsets
      2) The setting is applied right after pressing OK in the
         configuration dialog
      3) Qt fetches this updated info after tablet proximity leave/enter
    • Alvin Wong's avatar
      ext_vc: Make it not rely on a fixed install path · f0f35797
      Alvin Wong authored
      ... so that the deps install can be moved to another path. Makes it
      easier to reuse the deps built on the binary factory.
      Note: This does not guarantee that other deps will work when moved.
  13. 15 Apr, 2019 2 commits
    • Dmitry Kazakov's avatar
      Fetch tablet mapping from Wintab instead virtual screen geometry · 31c48ac7
      Dmitry Kazakov authored
      Some devices, like Microsoft Surface Pro 5, don't map tablet's
      input range to the entire virtual screen area, but map it to
      the primary display that has actual built-in tablet sensor.
      In such cases we should fetch actualy mapped aread from Wintab's
      lcSys{Org,Ext}{X,Y} fields and use it for cursor mapping.
      The patch also introduces an environment variable switch that
      falls back to the old method of mapping:
      When the variable is set, the scaling is done via virtual desktop
      area only.
    • Boudewijn Rempt's avatar
  14. 14 Apr, 2019 1 commit
  15. 13 Apr, 2019 3 commits
  16. 12 Apr, 2019 1 commit
  17. 11 Apr, 2019 1 commit