1. 02 Dec, 2021 1 commit
  2. 20 Feb, 2021 1 commit
  3. 31 Aug, 2020 1 commit
    • Carlos Garnacho's avatar
      gdk: Keep a reference on the last source device · a9800197
      Carlos Garnacho authored
      This device may go away, which means we have a pointer to a possibly
      stale object. Keep a reference here, and let future events bring this
      accounting up-to-date when the mouse pointer is next updated via other
      device.
      
      Fixes: #855
      a9800197
  4. 06 Sep, 2019 1 commit
  5. 02 Aug, 2019 1 commit
  6. 01 Jun, 2019 1 commit
    • Christian Hergert's avatar
      va_marshaller: add various va_marshallers · 6033b645
      Christian Hergert authored
      We don't need to cover every case with a va_marshaller, but there are a
      number of them that are useful because they will often only be connected
      to by a single signal handler.
      
      Generally speaking, if I opened into a file to add a va_marshaller, I just
      set all of them.
      6033b645
  7. 07 May, 2019 1 commit
    • Sebastian Dröge's avatar
      GdkWindow - Don't call unimplemented NULL set_startup_id() vfunc on Win32 · 02d4fbe2
      Sebastian Dröge authored
      GdkWindow::set_startup_id() is NULL on Win32 and would cause a segfault
      if called.
      
      While the documentation of the main caller of set_startup_id(),
      gtk_window_set_startup_id(), mentions that it's not implemented on
      Windows it can still be automatically called via Glade and simply doing
      nothing on Win32 is going to be less disruptive than a segfault.
      02d4fbe2
  8. 22 Feb, 2019 1 commit
  9. 12 Dec, 2018 1 commit
  10. 05 Jun, 2018 1 commit
    • Jonas Ådahl's avatar
      gdk: Make gdk_window_move_to_rect public · 9b3c745f
      Jonas Ådahl authored
      This is the API used by GtkMenu to properly position menus on the screen
      without requiring GTK to query the menu window's position or the work
      area of where the window is positioned. It makes it possible to position
      popup windows properly when using Wayland.
      
      Make this API available to external users so custom popup windows can be
      positioned properly as well.
      
      Closes: #997
      9b3c745f
  11. 25 May, 2018 1 commit
  12. 30 Nov, 2017 1 commit
    • Carlos Garnacho's avatar
      gdk: Always emit motion after enter · 3c40b217
      Carlos Garnacho authored
      After a pointer emulating GDK_TOUCH_END event triggering a fake leave
      notify with GDK_CROSSING_TOUCH_END mode, pointer_under_window will be
      unset, which will make the next motion/touch_update event to trigger
      an enter notify event again.
      
      Up till there, that's fine, however the motion event is just consumed
      in favor of the just synthesized enter notify event. This is unexpected
      to clients like spice-gtk that will only update coordinates from motion
      events, sending both enter and motion is more consistent with X11 and
      will make them happy.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=791039
      3c40b217
  13. 25 Oct, 2017 1 commit
  14. 18 Aug, 2017 1 commit
  15. 25 Jul, 2017 1 commit
  16. 03 Apr, 2017 1 commit
    • Olivier Fourdan's avatar
      gdkwindow: different displays, different classes · efbe4021
      Olivier Fourdan authored
      GdkWindow's before_process_all_updates() and after_process_all_updates()
      wrongly assume that all displays are from the same class, which is not
      the case if for example a client open different displays with different
      backends such as X11 and Wayland.
      
      Use the actual class for each display in the display list to avoid a
      crash when mixing displays from different classes.
      
      Fix suggested by Christian Persch <chpe@gnome.org> in bug #776472.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=776472
      efbe4021
  17. 23 Feb, 2017 1 commit
    • Olivier Fourdan's avatar
      gdkwindow: subsurface in gdk_window_get_effective_parent() · e5b63759
      Olivier Fourdan authored
      When the GtkWidget hierarchy does not match the GdkWindow hierarchy, the
      GtkWidget code may find a common ancestor that cannot be found while
      traversing the GdkWindow tree using gdk_window_get_effective_parent().
      
      This happens with for example on Wayland, a GtkPopover has another
      GtkPopover as parent, in this case, the GdkWindow parent is the root
      window, whereas the GtkWidget parent is the other GtkPopover.
      
      That confuses the gtk_widget_translate_coordinates() logic which will
      bail out in this case and won't return the translated coordinates.
      
      Make gdk_window_get_effective_parent() aware of subsurfaces and use the
      transient_for which represents the actual parent (whereas the parent
      might be pointing to the root window).
      
      Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=774148
      e5b63759
  18. 11 Jan, 2017 1 commit
  19. 17 Dec, 2016 1 commit
  20. 05 Dec, 2016 1 commit
  21. 30 Nov, 2016 1 commit
  22. 24 Nov, 2016 1 commit
  23. 18 Nov, 2016 1 commit
  24. 14 Nov, 2016 2 commits
  25. 21 Oct, 2016 1 commit
  26. 20 Oct, 2016 2 commits
  27. 17 Oct, 2016 1 commit
  28. 13 Oct, 2016 1 commit
    • Olivier Fourdan's avatar
      gdkwindow: configure native windows in move_native_children() · 12579fe7
      Olivier Fourdan authored
      ClutterEmbed on Wayland uses a subsurface and relocates it on configure
      events, but when placed within a scrolled window, no configure event is
      emitted and the ClutterEmbed subsurface remains static.
      
      Emit a configure event for native windows in GdkWindow's internal
      move_native_children() so that custom widgets relying on configure
      events such as ClutterEmbed can relocate their stuff.
      
      Similarly, when switching to/from normal/maximized/fullscreen states
      which change the shadows' size and possibly shows/hides a header bar,
      we need to emit a configure event even if the abs_x/abs_y haven't
      changed to make sure the subsurface is size appropriately.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=771320
      https://bugzilla.gnome.org/show_bug.cgi?id=767713
      12579fe7
  29. 24 Aug, 2016 1 commit
  30. 23 Aug, 2016 2 commits
  31. 07 Aug, 2016 1 commit
  32. 19 Jul, 2016 3 commits
  33. 11 Jul, 2016 1 commit
  34. 12 Jun, 2016 1 commit
  35. 09 Jun, 2016 1 commit