1. 12 Sep, 2020 1 commit
    • Matthias Clasen's avatar
      Clean up lots of GTK+ -> GTK · 929a56e5
      Matthias Clasen authored
      Replace most remaining uses of GTK+ in the docs and
      user-visible strings by GTK. Also remove some leftover
      "Was added in 3.x" sentences from the docs.
  2. 21 Aug, 2020 1 commit
  3. 05 Aug, 2020 1 commit
  4. 31 Jul, 2020 1 commit
    • Carlos Garnacho's avatar
      gdk: Fix toplevel calculation on pointer grab switch · 9564cba4
      Carlos Garnacho authored
      This check used to read if (grab || device_type != GDK_DEVICE_TYPE_PHYSICAL),
      the grab check was only reserved to physical devices, which the current
      pointer device definitely doesn't act like. So the condition was "fixed" the
      wrong way around, and the latter check is now moot, so the condition should
      really go away. We always want to check the new toplevel under the pointer
      Fixes: #2970
  5. 30 Jul, 2020 4 commits
  6. 28 Jul, 2020 2 commits
  7. 24 Jul, 2020 2 commits
  8. 23 Jun, 2020 1 commit
  9. 18 Jun, 2020 1 commit
    • Emmanuele Bassi's avatar
      Rename master and slave device · 1c856a20
      Emmanuele Bassi authored
      We already use the "logical/virtual" and "physical" names in the
      documentation, there's no reason to use loaded terms just because X11
      uses them.
  10. 31 May, 2020 2 commits
    • Christoph Reiter's avatar
      Drop fallback-c89.c · 2d5cf2b4
      Christoph Reiter authored
      We require a C compiler supporting C99 now. The main purpose of
      these fallbacks was for MSVC. From what I can see this is now all supported
      by MSVC 2015+ anyway.
      The only other change this includes is to replace isnanf() with the
      (type infering) C99 isnan() macro, because MSVC doesn't provide isnanf().
    • Emmanuele Bassi's avatar
      docs: Fix annotations · 43e5ca9a
      Emmanuele Bassi authored
       - Use the same name for the argument in the declaration, definition,
         and documentation
       - Use "optional" instead of the deprecated "allow-none"
  11. 29 May, 2020 1 commit
  12. 28 May, 2020 2 commits
  13. 19 May, 2020 1 commit
  14. 18 May, 2020 3 commits
  15. 17 May, 2020 2 commits
  16. 15 May, 2020 1 commit
  17. 13 May, 2020 2 commits
  18. 16 Apr, 2020 1 commit
    • Emmanuele Bassi's avatar
      Restructure the GdkEvent type hierarchy · f28aa1ba
      Emmanuele Bassi authored
      GdkEvent has been a "I-can't-believe-this-is-not-OOP" type for ages,
      using a union of sub-types. This has always been problematic when it
      comes to implementing accessor functions: either you get generic API
      that takes a GdkEvent and uses a massive switch() to determine which
      event types have the data you're looking for; or you create namespaced
      accessors, but break language bindings horribly, as boxed types cannot
      have derived types.
      The recent conversion of GskRenderNode (which had similar issues) to
      GTypeInstance, and the fact that GdkEvent is now a completely opaque
      type, provide us with the chance of moving GdkEvent to GTypeInstance,
      and have sub-types for GdkEvent.
      The change from boxed type to GTypeInstance is pretty small, all things
      considered, but ends up cascading to a larger commit, as we still have
      backends and code in GTK trying to access GdkEvent structures directly.
      Additionally, the naming of the public getter functions requires
      renaming all the data structures to conform to the namespace/type-name
  19. 06 Apr, 2020 3 commits
  20. 14 Mar, 2020 1 commit
  21. 21 Feb, 2020 4 commits
  22. 30 Jan, 2020 1 commit
    • Matthias Clasen's avatar
      Remove primary monitor api · a46f9af1
      Matthias Clasen authored
      We only have implementations of this on X11 and Win32,
      so make it available as backend api there.
      Update all callers to use either the backend api, or
      just monitor 0.
  23. 31 May, 2019 1 commit
    • Christian Hergert's avatar
      gtk: rely on default marshallers · bd26cce8
      Christian Hergert authored
      Similar to previous removals of g_cclosure_marshal_VOID__VOID we can remove
      other marshallers for which are a simple G_TYPE_NONE with single parameter.
      In those cases, GLib will setup both a c_marshaller and va_marshaller for
      us. Before this commit, we would not get a va_marshaller because the
      c_marshaller is set.
      Related to Initiatives#10
  24. 29 May, 2019 1 commit
    • Christian Hergert's avatar
      marshallers: ensure g_cclosure_marshal_VOID__VOIDv is used · f507a790
      Christian Hergert authored
      If we set c_marshaller manually, then g_signal_newv() will not setup a
      va_marshaller for us. However, if we provide c_marshaller as NULL, it will
      setup both the c_marshaller (to g_cclosure_marshal_VOID__VOID) and
      va_marshaller (to g_cclosure_marshal_VOID__VOIDv) for us.