1. 19 Oct, 2016 2 commits
    • Andreas Wettstein's avatar
      XIM: Allow modifier releases in compose sequences (#26705) · 4ef27790
      Andreas Wettstein authored
      Currently, only non-modifier keys (actually, keysyms) can be part of a compose
      sequence, and they are matched against the defined compose sequences at the
      time the key is pressed.  The patch allows to use modifier keys an well, but
      matches them on key release, and only if no other key has been pressed after
      the modifier.
      
      Releasing a non-matched modifier during an ongoing compose sequence only aborts
      the sequence if any modifier release would have matched.  In particular, if no
      compose sequences with modifiers are specified, the compose mechanism works
      exactly as without this patch.
      
      Even if modifiers are part of a compose sequence, they are not filtered.  This
      is because modifiers affect the keyboard state no matter what we do here and,
      therefore, filtering them only could confuse clients.
      
      The purpose is this extension to the compose mechanism is to allow to make
      better use of keys in convenient reach for touch typing.
      Signed-off-by: 's avatarAndreas Wettstein <wettstein509@solnet.ch>
      Signed-off-by: 's avatarJames Cloos <cloos@jhcloos.com>
      Backported-to-NX-by: 's avatarUlrich Sibiller <uli42@gmx.de>
      4ef27790
    • Samuel Thibault's avatar
      Match braille patterns with compose tree · b8b885da
      Samuel Thibault authored
      Braille patterns should also be usable in Compose.  This combines the
      implementation of braille chords and compose tree: only emit the braille
      pattern if it can not be found in the compose tree, if any.
      Signed-off-by: 's avatarSamuel Thibault <samuel.thibault@ens-lyon.org>
      Backported-to-NX-by: 's avatarUlrich Sibiller <uli42@gmx.de>
      b8b885da
  2. 10 Oct, 2016 1 commit
  3. 05 Jul, 2016 2 commits
  4. 28 Dec, 2015 1 commit
    • Mike Gabriel's avatar
      Clear header file namespace separation (<X11/...> vs. <nx-X11/...>). · 433d8186
      Mike Gabriel authored
       In the process of building nxagent against more and more system-wide installed
       X.org libraries, we come to the limit of including structs from this (bundled
       nx-X11) and that (system-wide X.Org) library.
      
       This commit introduces a clear namespace separation of headers provided by
       nx-X11 and headers provided by X.Org. This approach is only temporary as we
       want to drop all nx-X11 bundled libraries from nx-libs.
      
       However, for a while we need to make this separation clear and also ship
       some reduced fake X.Org headers that avoid pulling in libX* and libNX_X*
       symbols at the same time.
      
       This patch has been tested on Debian jessie and unstable and requires no
       overall testing on various distros and distro versions, as we finally will
       drop all libNX_X* libraries and build against X.org's client libs.
      
       For now, this hack eases our development / cleanup process.
      433d8186
  5. 10 Oct, 2011 1 commit