1. 10 Mar, 2016 5 commits
  2. 24 Feb, 2016 2 commits
  3. 23 Feb, 2016 2 commits
  4. 22 Feb, 2016 1 commit
  5. 16 Feb, 2016 1 commit
  6. 28 Jan, 2016 10 commits
  7. 07 Jan, 2016 3 commits
  8. 17 Dec, 2015 2 commits
    • Paolo Borelli's avatar
      Win32: call dnd exit when finalizing the display · f74c55fb
      Paolo Borelli authored
      Since we init dnd when opening the display, call the corresponding
      exit function (which is unused at the moment) when finalizing the
    • Paolo Borelli's avatar
      Win32: move CoInitialize to dnd init · c9f370a1
      Paolo Borelli authored
      Functions requiring CoInitialize are called just in two places:
       - the filechooser thread which calls its own CoInitializeEx
       - the dnd code
      Moving CoInitialize in the dnd specific init is cleaner and
      we can pair it with the corresponding CoUninitialize since
      CoUninitialize should be called as many times as CoInitialize.
      Note that it is ok to call this function multiple times, so it
      will not break if another codepath will need it in the future.
      The patch also replaces the deprecated CoInitialize with the
      equivalent call to CoInitializeEx (already used in the filechooser).
  9. 16 Dec, 2015 1 commit
    • Lars Uebernickel's avatar
      gdk_pixbuf_get_from_surface: restore old behavior · 2cbc2972
      Lars Uebernickel authored
      A previous commit changed this function to return a pixbuf that is
      larger than the passed (width, height) when the surface has a device
      scale > 1. It's easy enough to take care of a scaled surface before
      calling this function.
      Revert to the old behaviour, but change gdk_pixbuf_get_from_window() to
      return a scaled version when the underlying surface is scaled. We need
      this because there's no other way to get to the unscaled window
  10. 05 Dec, 2015 8 commits
  11. 03 Dec, 2015 2 commits
  12. 30 Nov, 2015 1 commit
    • Carlos Garnacho's avatar
      wayland: Refactor selection ownership · 9db511f6
      Carlos Garnacho authored
      Dissociate ownership from our maintenance of wl_data_source objects.
      The only place where ownership must be updated together is
      data_source.cancelled, for the other places GDK should take care of
      setting up the right ownership, even if at a different order than
      we'd expect here.
      This fixes GTK+ apps on wayland being locally confused about the
      current selection ownership. Because gtk_selection_add_targets()
      results in a wl_data_source being created, and ownership being
      updated right away, early callers of this will change the ownership
      even if the widget it's being called on didn't explicitly request
      the selection ownership yet.
  13. 25 Nov, 2015 2 commits