1. 25 Nov, 2018 1 commit
  2. 18 Nov, 2018 1 commit
  3. 17 Aug, 2018 1 commit
  4. 08 Jan, 2018 1 commit
  5. 26 Jan, 2017 5 commits
  6. 17 Nov, 2016 1 commit
  7. 16 Aug, 2016 1 commit
  8. 20 Mar, 2014 3 commits
  9. 10 Oct, 2013 1 commit
  10. 16 Jan, 2013 4 commits
    • Sascha Hlusiak's avatar
      joystick 1.6.2 · 426c3aa3
      Sascha Hlusiak authored
      Signed-off-by: Sascha Hlusiak's avatarSascha Hlusiak <saschahlusiak@arcor.de>
    • Sascha Hlusiak's avatar
      config: warning in default xorg.conf.d snippet: do not enable by default · 8f934248
      Sascha Hlusiak authored
      see discussion: https://bugs.gentoo.org/show_bug.cgi?id=403003
      distributions should not ship the module enabled by default, because a lot
      of users have the joystick module installed without knowing, resulting in
      confusion and bad user experience when trying to play games, the more
      likely usecase when plugging in a joystick.
      the default configuration only fits for a limited number of users.
      it does not make much sense to automatically enable hotplugging of the
      module without explicit user consent and reviewing of the configuration.
      Signed-off-by: Sascha Hlusiak's avatarSascha Hlusiak <saschahlusiak@arcor.de>
    • Sascha Hlusiak's avatar
      jast_axis: tune accelerated axis transformation to better work with circular axis fields · 819ba33c
      Sascha Hlusiak authored
      reference: https://bugs.freedesktop.org/show_bug.cgi?id=42399
      joysticks with a rectangular field have a
      corner position of (32768,32768), joysticks with a
      circular field have (23170,23170).
      make sure that diagonal movement feels fast. either:
      1) linear
        f(32768) ~= f(23170) + f(23170)
        f(32768) ~= a * f(23170)
               a  = 2.0
        on circular joysticks, the time needed for xy movement is
        exactly the time needed for x + the time for y separately.
        absolute diagonal travel speed (in cm/s) is 0.707 times as fast,
        which feels pretty slow.
        on square joysticks, diagonal travel speed is always 1.41 times
        faster than orthogonal travel speed. time needed for diagonal
        movement is always 0.5 times as long as for orthogonal movement.
        the value of a = 2.0 results in a nice, non-linear acceleration.
      2) trigonometric
        f(32768) ~= sqrt(f(23170)^2 + f(23170)^2))
        f(32768) ~= a * f(23170)
        a = 1.414
      on circular joysticks, the absolute pointer travel speed
      (in cm/s) is now the same for both linear and diagonal movement,
      which feels natural. moving diagonally takes 0.707 times the time
      of moving orthogonally.
      on square joysticks, values are as in 1)
      the value of a = 1.414 results in linear acceleration, which feels
      too slow.
      to maintain non-linear acceleration, make sure that:
      a >>= 1.414
      the following formula achieves results inbetween,
      so it should feel natural on both devices while maintaining a
      nice acceleration:
      f(32768) ~= 1.620 * f(23170)
    • Sascha Hlusiak's avatar
      backend_evdev: fix scaling overflow for high resolution axes · 342057bf
      Sascha Hlusiak authored
      The module scales all axis values from the kernel to the range of
      -32768 .. 32768, for compatibility with the old joystick kernel module.
      The current implementation had an integer overflow, if the axis had a high
      resolution of > 16384, like the popular XBox 360 controller.
      This commitmakes the scaling use float instead to fix erratic behaviour
      on high resolution joysticks. The joystick backend was not affected.
      Fixes bug: https://bugs.freedesktop.org/show_bug.cgi?id=42399
  11. 13 Jan, 2013 1 commit
  12. 03 Oct, 2012 6 commits
  13. 25 Sep, 2012 1 commit
  14. 11 Mar, 2012 1 commit
  15. 13 Nov, 2011 3 commits
  16. 01 Nov, 2011 1 commit
  17. 31 Oct, 2011 1 commit
  18. 15 Oct, 2011 1 commit
    • Sascha Hlusiak's avatar
      label buttons and axes · b607c4eb
      Sascha Hlusiak authored
      Buttons are labeled "Button %d", starting with 0 and representing the button in X _after_ mapping.
      Mapping can be changed while running so the labels will be constant.
      Axes are labeled "Axis %d", starting with 1, representing the _physical_ axis that reports the valuator
      data. The raw valuators can't be dynamically mapped, the first two valuators always are labeled "Rel X"
      and "Rel Y", representing the aggregated post-calculation data from all axes.
      Signed-off-by: Sascha Hlusiak's avatarSascha Hlusiak <saschahlusiak@arcor.de>
  19. 06 Sep, 2011 1 commit
  20. 18 Jul, 2011 1 commit
  21. 20 Apr, 2011 4 commits