1. 27 Feb, 2012 1 commit
  2. 24 Feb, 2012 1 commit
  3. 05 Jan, 2012 1 commit
  4. 02 Nov, 2011 2 commits
    • Benjamin Otte's avatar
      gdk: Move a bunch of deprecated code to a new file · b120cb04
      Benjamin Otte authored
      The new file defines GDK_DISABLE_DEPRECATION_WARNINGS so it can happily
      use deprecated APIs.
      
      This commit moves those functions there that use deprecated functions
      and currently cause warnings.
      
      With this commit, GDK compiles without deprecation warnings.
      b120cb04
    • Benjamin Otte's avatar
      display: Don't use deprecated functions · c9a64839
      Benjamin Otte authored
      When synthesizing crossing events, actually query the position of the
      device we care about instead of using the core pointer every time.
      c9a64839
  5. 03 Oct, 2011 1 commit
    • Adel Gadllah's avatar
      gdk: Plug leak in gdk_display_pointer_is_grabbed · 25e65dc1
      Adel Gadllah authored
      gdk_x11_device_manager_core_list_devices returns a new allocated
      list, which has to be freed.
      
      valgrind output:
      
      ==18686== 160,176 (80,088 direct, 80,088 indirect) bytes in 3,337 blocks are definitely lost in loss record 25,347 of 25,378
      ==18686==    at 0x4C256DD: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==18686==    by 0x6CD7752: g_malloc (in /lib64/libglib-2.0.so.0.3000.0)
      ==18686==    by 0x6CEE2B6: g_slice_alloc (in /lib64/libglib-2.0.so.0.3000.0)
      ==18686==    by 0x6CCB37D: g_list_prepend (in /lib64/libglib-2.0.so.0.3000.0)
      ==18686==    by 0x654CADA: gdk_x11_device_manager_core_list_devices (gdkdevicemanager-core-x11.c:836)
      ==18686==    by 0x6531489: gdk_display_pointer_is_grabbed (gdkdisplay.c:1270)
      ==18686==    by 0x5162E1E: filter_func (ui.c:140)
      ==18686==    by 0x6558B50: gdk_event_apply_filters (gdkeventsource.c:83)
      ==18686==    by 0x6558CB3: _gdk_x11_display_queue_events (gdkeventsource.c:197)
      ==18686==    by 0x6530680: gdk_display_get_event (gdkdisplay.c:311)
      ==18686==    by 0x65589F1: gdk_event_source_dispatch (gdkeventsource.c:356)
      ==18686==    by 0x6CD0A0E: g_main_context_dispatch (in /lib64/libglib-2.0.so.0.3000.0)
      
      https://bugzilla.gnome.org/show_bug.cgi?id=660676
      25e65dc1
  6. 10 Jun, 2011 1 commit
  7. 16 May, 2011 1 commit
  8. 09 Apr, 2011 1 commit
  9. 21 Mar, 2011 1 commit
  10. 08 Mar, 2011 1 commit
  11. 28 Feb, 2011 1 commit
  12. 09 Feb, 2011 1 commit
    • Matthias Clasen's avatar
      Give the GDK docs some love · 1f4bb70b
      Matthias Clasen authored
      Reorganize some sections, drop the largely redundant multihead
      section, add some more information about multiple backends.
      1f4bb70b
  13. 08 Feb, 2011 1 commit
  14. 01 Feb, 2011 2 commits
    • Benjamin Otte's avatar
      API: gdk: Change get_drag_window() API · 44c02fcb
      Benjamin Otte authored
      The previous function gdk_drag_get_protocol_for_display() took native
      window handles, so it had to be changed. Because it didn't do what it
      was named to do (it didn't return a protocol even though it was named
      get_protocol) and because it doesn't operate on the display anymore but
      on the actual window, it's now called gdk_window_get_drag_protocol().
      44c02fcb
    • Benjamin Otte's avatar
      gdk: Remove GdkEventClient · c332ac20
      Benjamin Otte authored
      ... and all APIs making use of it.
      
      That code like it hasn't been touched in years, Google codesearch
      didn't find any users and most importantly it's a horrendous API, so
      let's just make it die instead of having to port it over to
      non-GdkNativeWindow usage, which would be required for multi-backend
      GDK.
      
      http://mail.gnome.org/archives/gtk-devel-list/2011-January/msg00049.html
      c332ac20
  15. 24 Jan, 2011 1 commit
    • Carlos Garnacho's avatar
      Avoid toplevel tracking on slave device after ungrab · 5fd5872b
      Carlos Garnacho authored
      slave devices don't have coordinates themselves, as they depend
      on a master, this only changes if they have a grab in effect,
      so only keep toplevel tracking enabled in such situation. Fixes
      Bug #640313 - BadDevice X error when ungrabbing a SLAVE device,
      noticed by Jesse van den Kieboom.
      5fd5872b
  16. 20 Jan, 2011 3 commits
  17. 03 Jan, 2011 6 commits
  18. 27 Dec, 2010 2 commits
  19. 25 Dec, 2010 1 commit
  20. 24 Dec, 2010 1 commit
  21. 21 Dec, 2010 10 commits