Skip to content
Snippets Groups Projects
  1. Apr 24, 2013
  2. Apr 17, 2013
  3. Apr 08, 2013
  4. Apr 02, 2013
  5. Mar 26, 2013
  6. Mar 25, 2013
  7. Mar 18, 2013
  8. Mar 13, 2013
  9. Mar 12, 2013
  10. Mar 08, 2013
  11. Mar 06, 2013
    • Keith Packard's avatar
      Version bumped to 1.14 · 103b77c5
      Keith Packard authored
      
      Signed-off-by: default avatarKeith Packard <keithp@keithp.com>
    • Andreas Wettstein's avatar
      xkb: Fixes to LatchMods/LatchGroup · 0f537da7
      Andreas Wettstein authored and Peter Hutterer's avatar Peter Hutterer committed
      
      The main problem this patch addresses is that if a latch is put on
      multi-level key with a Latch/Lock/Set, it is possible that after all
      keys are released, still base modifiers are set, which typically will
      make the keyboard unusable.  To see how it happens (without the patch),
      assume that key AltGr sets Mod5 when pressed by itself, and latches Mod3
      when pressed together with Shift.  Now press Shift, then AltGr and
      release both keys in reverse order.  Mod3 is now latched, and the
      LatchMods filter remains active as the second filter.  Now press AltGr;
      Mod5 base modifier gets set, and the SetMods filter will become active
      as the first filter.  Release AltGr: First, the SetMods filter will set
      clearMods to Mod5, then the LatchMods filter will overwrite clearMods
      with Mod3.  Result: the Mod5 base modifier will remain set.  This
      example becomes practically relevant for the revised German standard
      layout (DIN 2137-1:2012-06).
      
      Other changes implement the latch behaviour more accurately according to
      the specification.  For example, releasing a modifier latching key can
      at the same time clear a locked modifier, promote another modifier that
      is latched to locked, and latch a third modifier.  Overall, what the
      code does should be straightforward to compare what the XKB protocol
      specification demands, see the table in section 6.3.
      
      Finally, releasing a key no longer cancels a latch that has not become
      pending yet.  In my opinion, the specification is not clear; it speaks
      of "operating" a key, which the patch effectivly interprets as "press"
      rather than "press or release".  From my experience, using the latter
      interpretation makes latches on higher levels practically unusable.  In
      the example given above, one would have to release AltGr always before
      Shift to get the Mod3-Latch.  The practical relevance of latches on
      higher levels is once more given by the revised German standard layout.
      
      Signed-off-by: default avatarAndreas Wettstein <wettstein509@solnet.ch>
      Reviewed-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      0f537da7
    • Peter Hutterer's avatar
      xephyr: fix "set but not used warnings" · eadda231
      Peter Hutterer authored
      
      ephyrvideo.c: In function 'ephyrPutVideo':
      ephyrvideo.c:1009:42: warning: variable 'drw_h' set but not used
      ephyrvideo.c:1009:31: warning: variable 'drw_w' set but not used
      ephyrvideo.c:1009:20: warning: variable 'drw_y' set but not used
      ephyrvideo.c:1009:9: warning: variable 'drw_x' set but not used
      ephyrvideo.c: In function 'ephyrGetVideo':
      ephyrvideo.c:1058:42: warning: variable 'drw_h' set but not used
      ephyrvideo.c:1058:31: warning: variable 'drw_w' set but not used
      ephyrvideo.c:1058:20: warning: variable 'drw_y' set but not used
      ephyrvideo.c:1058:9: warning: variable 'drw_x' set but not used
      ephyrvideo.c: In function 'ephyrPutStill':
      ephyrvideo.c:1107:42: warning: variable 'drw_h' set but not used
      ephyrvideo.c:1107:31: warning: variable 'drw_w' set but not used
      ephyrvideo.c:1107:20: warning: variable 'drw_y' set but not used
      ephyrvideo.c:1107:9: warning: variable 'drw_x' set but not used
      ephyrvideo.c: In function 'ephyrGetStill':
      ephyrvideo.c:1156:42: warning: variable 'drw_h' set but not used
      ephyrvideo.c:1156:31: warning: variable 'drw_w' set but not used
      ephyrvideo.c:1156:20: warning: variable 'drw_y' set but not used
      ephyrvideo.c:1156:9: warning: variable 'drw_x' set but not used
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarRobert Morell <rmorell@nvidia.com>
      eadda231
    • Peter Hutterer's avatar
      kdrive: fix "set but not used" warnings · 4149ee8e
      Peter Hutterer authored
      
      kinput.c: In function 'KdEnqueueKeyboardEvent':
      kinput.c:1845:16: warning: variable 'ctrl' set but not used
      kinput.c:1844:17: warning: variable 'keyc' set but not used
      
      kinput.c: In function 'KdEnqueuePointerEvent':
      kinput.c:1887:12: warning: variable 'ms' set but not used
      
      kxv.c: In function 'KdXVDisable':
      kxv.c:1181:19: warning: variable 'ScreenPriv' set but not used
      
      mouse.c: In function 'ps2SkipInit':
      mouse.c:444:9: warning: variable 'skipping' set but not used
      mouse.c: In function 'ps2Init':
      mouse.c:473:10: warning: variable 'waiting' set but not used
      mouse.c:472:9: warning: variable 'skipping' set but not used
      
      fbdev.c: In function 'fbdevRandRSetConfig':
      fbdev.c:468:19: warning: variable 'newheight' set but not used
      fbdev.c:468:9: warning: variable 'newwidth' set but not used
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarRobert Morell <rmorell@nvidia.com>
      4149ee8e
  12. Mar 05, 2013
  13. Mar 04, 2013
  14. Mar 01, 2013
Loading