1. 07 Feb, 2014 2 commits
  2. 09 Jan, 2014 1 commit
  3. 02 Aug, 2013 1 commit
  4. 16 Apr, 2013 1 commit
    • Benjamin Otte's avatar
      gdk: Unvfuncify generic key functions · 0990c11a
      Benjamin Otte authored
      This makes Wayland and X11 no longer call into XKB and libX11 for these
      functions but use GDK's own copy of these functions, just like the
      win32, quartz and broadway backends.
      0990c11a
  5. 09 Sep, 2012 1 commit
    • Matthias Clasen's avatar
      Be more strict in ignoring ineffective modifiers · eb9223c0
      Matthias Clasen authored
      After my recent fix for this, nautilus was still having problems
      telling keeping F10 and Shift-F10 apart. With this change, we are
      treating levels with the same symbol like inactive levels, ignoring
      them entirely.
      eb9223c0
  6. 02 Sep, 2012 1 commit
    • Matthias Clasen's avatar
      Try harder to discriminate Shift-F10 and F10 · 314b6abb
      Matthias Clasen authored
      A change in xkeyboard-config 2.4.1 made it so that function keys
      now have a shift level which has the same symbol, but 'eats' the
      shift modifier. This would ordinarily make it impossible for us
      to discriminate between these key combinations.
      
      This commit tries harder to discriminate in 2 ways:
      - XKB has a mechanism to tell us when a modifier should not be
        consumed even though it was used in determining the level.
        We now respect such 'preserved' modifiers. This does not fix
        the Shift-F10 vs F10 problem yet, since xkeyboard-config does
        not currently mark Shift as preserved for function keys.
      - Don't consume modifiers that do not change the symbol. For
        the function keys, the symbol on the shift level is the same
        as the base level, so we don't consider Shift consumed.
      
      For more background on the xkeyboard-config change, see
      https://bugs.freedesktop.org/show_bug.cgi?id=45008
      
      https://bugzilla.gnome.org/show_bug.cgi?id=661973
      314b6abb
  7. 30 Apr, 2012 1 commit
  8. 11 Mar, 2012 1 commit
  9. 27 Feb, 2012 1 commit
  10. 21 Feb, 2012 1 commit
  11. 19 Feb, 2012 1 commit
    • Bastien Nocera's avatar
      x11: Fix first call to _gdk_x11_keymap_key_is_modifier() · 6697d5c6
      Bastien Nocera authored
      _gdk_x11_keymap_key_is_modifier() never tries to set min/max_keycode
      if they haven't been set before, meaning that until another function
      sets those, all the keys will be seen as non-modifiers.
      
      This causes GdkKeyEvents to be wrongly tagged with "->is_modifier = 0"
      when in actual fact the key is a modifier. This fixes keyboard
      shortcuts captured with GtkCellRendererAccel in "raw" mode thinking
      a modifier without any actual keys is a valid shortcut.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=670400
      6697d5c6
  12. 18 Nov, 2011 3 commits
  13. 07 Nov, 2011 1 commit
    • Michael Natterer's avatar
      gdk: exclude MOD1 from the virtual modifier mapping · ac943bf6
      Michael Natterer authored
      which effectively nails down the MOD1 == ALT assumption that is valid
      in all other parts of GTK+. After the modifier abstraction fixes for
      OSX, the virtual mapping is now (correctly) used in more places, and
      caused problems with the common default PC keyboard layout on X11 that
      colocates ALT and META on the same key.
      ac943bf6
  14. 07 Oct, 2011 1 commit
    • Michael Natterer's avatar
      gdk: fix gdk_keyval_to_lower/upper() for Quartz, Win32 and Broadway · 5b74ee38
      Michael Natterer authored
      In 2.x, the !HAVE_XCONVERTCASE fallback of keyval_convert_case() was
      implicitly used as implementation for all !X11 backends.
      
      In 3.x, when this function was virtualized in GdkDisplayManager,
      this fallback was moved to the X11 backend and the other backends
      "equipped" with /* FIXME implement */ implementations of
      keyval_convert_case() which don't convert anything.
      
      Move the fallback code back to gdk/ as default implementation
      of GdkDisplayManager::keyval_convert_case() and remove its
      implementations is all backends but X11. Also remove the
      implementation in Wayland which was a plain copy of what
      is now the default implementation.
      (cherry picked from commit f46c1b76)
      5b74ee38
  15. 22 Jul, 2011 1 commit
  16. 30 Jun, 2011 1 commit
  17. 03 Apr, 2011 1 commit
  18. 21 Dec, 2010 9 commits
  19. 03 Dec, 2010 1 commit
  20. 24 Nov, 2010 1 commit
  21. 13 Nov, 2010 1 commit
  22. 10 Nov, 2010 1 commit
  23. 15 Oct, 2010 1 commit
  24. 05 Oct, 2010 1 commit
  25. 08 Sep, 2010 1 commit
    • Colin Walters's avatar
      GDK: Prefix key names with KEY_ · 913cdf3b
      Colin Walters authored
      The keysyms create a lot of potential namespace conflicts for
      C, and are especially problematic for introspection, where we take
      constants into the namespace, so GDK_Display conflicts with GdkDisplay.
      
      For C application compatiblity, add gdkkeysyms-compat.h which uses
      the old names.
      
      Just one user in GTK+ continues to use gdkkeysyms-compat.h, which is
      the gtkimcontextsimple.c, since porting that requires porting more
      custom Perl code.
      913cdf3b
  26. 07 Sep, 2010 1 commit
  27. 25 Aug, 2010 1 commit
  28. 10 Jul, 2010 1 commit
  29. 02 Jul, 2010 1 commit