1. 04 Apr, 2019 1 commit
  2. 02 Apr, 2019 2 commits
  3. 01 Apr, 2019 3 commits
  4. 29 Mar, 2019 2 commits
    • Roman Gilg's avatar
      present: Call present_vblank_scrap in screen mode · 4adda1f6
      Roman Gilg authored and Michel Dänzer's avatar Michel Dänzer committed
      This cleans up some code duplication. No functional change.
      Signed-off-by: Roman Gilg's avatarRoman Gilg <subdiff@gmail.com>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <michel.daenzer@amd.com>
    • Peter Hutterer's avatar
      dix: leave last.valuators alone on slave switch · d7b1753d
      Peter Hutterer authored
      dev->last.valuator[] is the last value given to us by the driver
      dev->valuator.axisVal[] is the last value sent to the client
      dev->last.scroll[] is the abs value of the scroll axis as given by the driver,
              used for button emulation calculation (and the remainder)
      This function updates the device's last.valuator state based on the current
      master axis state. This way, relative motion continues fluidly when switching
      between devices. Before mouse 2 comes into effect, it's valuator state is
      updated to wherever the pointer currently is so the relative event applies on
      top of that.
      This can only work for x/y axes, all other axes aren't guaranteed to have the
      same meaning and/or may not be present:
      - xtest device: no valuator 2
      - mouse: valuator 2 is horizontal scroll axis
      - tablet: valuator 2 is pressure
      Scaling the current value from the pressure range into the range for
      horizontal scrolling makes no sense. And it causes scroll jumps:
      - scroll down, last.valuator == axisVal == 20
      - xdotool click 1, the XTest device doesn't have that valuator
      - scroll up
        - updateSlaveDeviceCoords reset last.valuator to 0 (axisVal == 20)
        - DeviceClassesChangedEvent includes value 20 for the axis
        - event is processed, last.value changes from 0 to -1
        - axisVal is updated to -1, causing a jump of -21
      The same applies when we switch from tablet to mouse wheel if the pressure
      value is 0 on proximity out (basically guaranteed). So let's drop this code
      altogether and only leave the scaling for the relative x/y motion.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  5. 28 Mar, 2019 8 commits
  6. 27 Mar, 2019 6 commits
  7. 20 Mar, 2019 2 commits
  8. 15 Mar, 2019 1 commit
  9. 14 Mar, 2019 1 commit
  10. 13 Mar, 2019 2 commits
  11. 11 Mar, 2019 3 commits
  12. 08 Mar, 2019 4 commits
  13. 06 Mar, 2019 1 commit
    • Andy Ritger's avatar
      xfree86/modes: Add "NoOutputInitialSize" option · e51ebc18
      Andy Ritger authored and Adam Jackson's avatar Adam Jackson committed
      Normally, the X server infers the initial screen size based on any
      connected outputs.  However, if no outputs are connected, the X server
      picks a default screen size of 1024 x 768.  This option overrides the
      default screen size to use when no outputs are connected.  In contrast
      to the "Virtual" Display SubSection entry, which applies unconditionally,
      "NoOutputInitialSize" is only used if no outputs are detected when the
      X server starts.
      Parse this option in the new exported helper function
      xf86AssignNoOutputInitialSize(), so that other XFree86 loadable drivers
      can use it, even if they don't use xf86InitialConfiguration().
      Signed-off-by: default avatarAndy Ritger <aritger@nvidia.com>
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
  14. 05 Mar, 2019 1 commit
    • Adam Jackson's avatar
      meson: Bump required meson version to 0.46 · 7e046b94
      Adam Jackson authored
      We were being naughty:
      WARNING: Project specifies a minimum meson_version '>= 0.42.0' but uses features which were added in newer versions:
       * 0.46.0: {'compiler.has_multi_link_argument', 'compiler.has_link_argument'}
  15. 27 Feb, 2019 1 commit
    • Michel Dänzer's avatar
      Revert "gitlab-ci: Only run docker-image stage if relevant source files change" · 0ec9a13c
      Michel Dänzer authored and Michel Dänzer's avatar Michel Dänzer committed
      This reverts commit 8694395f.
      Some scenarios have come to light where this failed to ensure the docker
      image exists:
      * If the master branch of a forked repository is used for an MR which
        doesn't modify .gitlab-ci.yml, the docker-image job may not run.
      * If the docker-image job of the first pipeline in a forked repository
        is cancelled or fails for any reason, and .gitlab-ci.yml isn't
        modified for the next pipeline run.
  16. 25 Feb, 2019 2 commits