1. 16 Jan, 2017 1 commit
    • Olivier Fourdan's avatar
      wayland: avoid 0 width/height anchor rectangle · 9a5ffcd1
      Olivier Fourdan authored
      Passing a rectangle with zero width or height to xdg_shell-v6
      set_anchor_rect() will cause a protocol error and terminate the client,
      as with gedit when pressing the Win key.
      
      Reason for this is because the rectangle used to set the anchor comes
      from gtk_text_layout_get_iter_location() which uses the pango layout
      width/height, which can be empty if there is not character at the given
      location.
      
      Make sure we don't use 0 as width or height as an anchor rectangle to
      avoid the protocol error, and compensate the logical position of the
      given rectangle if the size is changed, so that the actual position
      remains as expected by the client.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=777176
      9a5ffcd1
  2. 15 Jan, 2017 1 commit
  3. 13 Jan, 2017 2 commits
  4. 11 Jan, 2017 1 commit
  5. 10 Jan, 2017 4 commits
    • Rui Matos's avatar
      gdk/wayland: Handle non-existant gsettings keys · 99abc636
      Rui Matos authored
      Since we're a library, crashing on gsettings keys, whose presence is out
      of our control, isn't appropriate.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=775846
      99abc636
    • Rui Matos's avatar
      gdk/wayland: Add support for the gtk-enable-primary-paste gsetting · 22b1e0b6
      Rui Matos authored
      The gsetting was recently added so that we can have this configurable
      on the wayland backend too.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=775846
      22b1e0b6
    • LRN's avatar
      GDK W32: Use keyboard hook to detect AeroSnap combinations better · eece8a7d
      LRN authored
      Windows WM handles AeroSnap for normal windows on keydown. We did this
      on keyup only because we do not get a keydown message, even if Windows WM
      does nothing with a combination. However, in some specific cases it DOES
      do something - and we have no way to detect that. Specifically, winkey+downarrow
      causes maximized window to be restored by WM, and GDK fails to detect that. Then
      GDK gets a keyup message, figures that winkey+downarrow was pressed and released,
      and handles the combination - by minimizing the window.
      
      To overcome this, install a low-level keyboard hook (high-level ones have
      the same problem as normal message loop - they don't get messages when
      Windows WM handles combinations) and use it to detect interesting key combinations
      before Windows WM has a chance to block them from being processed.
      
      Once an interesting combination is detected, post a message to the window, which
      will be handled in due order.
      
      It should be noted that this code handles key repetitions in a very crude manner.
      
      The downside is that AeroSnap will not work if hook installation function call fails.
      Also, this is a global hook, and if the hook procedure does something wrong, bad things
      can happen.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=776031
      eece8a7d
    • LRN's avatar
      GDK W32: Handle CapsLock as part of the key shift level · ca792960
      LRN authored
      Instead of using some kind of flawed logic about modifying a keypress result
      when CapsLock is toggled, just add a CapsLock shift level (and all derived
      shift levels, i.e. Shift+CapsLock and CapsLock+AltGr and Shift+CapsLock+AltGr)
      and query Windows keyboard layout API about the result of keypresses involving
      CapsLock.
      
      Keysym table is going to be (roughly) twice as large now, but CapsLock'ed
      keypresses will give correct results for some keyboard layouts (such as
      Czech keyboard layout, which without this change produces lowercase letters
      for CapsLock->[0,2,3,4...] instead of uppercase ones).
      
      Keymap update time also increases accordingly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=165385
      ca792960
  6. 09 Jan, 2017 7 commits
  7. 08 Jan, 2017 1 commit
  8. 07 Jan, 2017 4 commits
  9. 06 Jan, 2017 3 commits
  10. 05 Jan, 2017 3 commits
  11. 04 Jan, 2017 4 commits
  12. 31 Dec, 2016 1 commit
    • Daniel Boles's avatar
      scrolledwindow: Fix func summary being cut off in bindings using doxygen · 7960e941
      Daniel Boles authored
      ...which treats the first '.' in doc comments as the end of the summary.
      So, e.g., in gtkmm, get_kinetic_scrolling() is currently summarised as
      "Changes the behaviour of @scrolled_window wrt." Not very informative!
      
      No need for a period there & anyway, the phrase "wrt to" is superfluous,
      and we have space to actually say "with regard to", so just do that now.
      7960e941
  13. 30 Dec, 2016 2 commits
  14. 29 Dec, 2016 2 commits
  15. 24 Dec, 2016 1 commit
  16. 20 Dec, 2016 2 commits
  17. 19 Dec, 2016 1 commit