1. 06 Sep, 2015 1 commit
  2. 02 Jun, 2015 1 commit
  3. 26 Apr, 2015 1 commit
  4. 10 Apr, 2015 1 commit
    • Matthias Clasen's avatar
      GtkApplication: Prevent more crashes around shutdown · 7603b527
      Matthias Clasen authored
      gtk_application_shutdown clears the impl member, so all
      callbacks, signal handlers, etc that might still be triggered
      between a shutdown call and the return from the mainloop
      better be prepared to deal with impl being NULL.
      7603b527
  5. 08 Apr, 2015 1 commit
  6. 02 Feb, 2015 1 commit
  7. 06 Sep, 2014 1 commit
  8. 19 Aug, 2014 1 commit
  9. 03 Aug, 2014 1 commit
  10. 30 Jul, 2014 1 commit
  11. 07 Jul, 2014 4 commits
  12. 03 Jul, 2014 1 commit
    • Allison Karlitskaya's avatar
      Add gtk_application_prefers_app_menu() · d3b34d3c
      Allison Karlitskaya authored
      Applications can call this to determine if they should an app menu.
      This will be %FALSE on desktop environments that do not have an
      application menu like the one in gnome-shell.  It is %FALSE on Windows
      and Mac OS.
      
      Applications are completely free to totally ignore this API -- it is
      only provided as a hint to help applications that may be interested in
      supporting non-GNOME platforms with a more native 'look and feel'.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=722092
      d3b34d3c
  13. 25 May, 2014 1 commit
  14. 11 May, 2014 1 commit
  15. 05 May, 2014 2 commits
  16. 06 Apr, 2014 1 commit
  17. 18 Mar, 2014 1 commit
  18. 13 Feb, 2014 1 commit
  19. 09 Feb, 2014 1 commit
  20. 07 Feb, 2014 1 commit
  21. 06 Feb, 2014 1 commit
  22. 05 Feb, 2014 2 commits
  23. 04 Feb, 2014 3 commits
  24. 29 Jan, 2014 2 commits
  25. 22 Jan, 2014 1 commit
  26. 18 Jan, 2014 1 commit
  27. 10 Jan, 2014 1 commit
  28. 26 Dec, 2013 1 commit
  29. 16 Dec, 2013 1 commit
    • Allison Karlitskaya's avatar
      Refactor GtkApplication · 7fd81cf1
      Allison Karlitskaya authored
      gtkapplication.c has turned into a bit of an #ifdef mess over time, and
      many of the current checks are incorrect.  As an example, if you build
      Gtk for wayland, and exclude the X11 backend, much of the functionality
      required by wayland (such as exporting menu models) will be disabled.
      
      Solve that by introducing a backend mechanism to GtkApplication (named
      GtkApplicationImpl) similar to the one in GApplication.  Add backends
      for Wayland, X11 and Quartz, with X11 and Wayland sharing a common
      'DBus' superclass.
      
                                   GtkApplicationImpl
                                            |
                             /--------------+-------------------\
                             |                                  |
                  GtkApplicationImplDBus              GtkApplicationImplQuartz
                             |
                 /-----------+-----------------\
                 |                             |
        GtkApplicationImplX11      GtkApplicationImplWayland
      
      GtkApplicationImpl itself is essentially a bunch of vfuncs that serve as
      hooks for various things that the platform-specific backends may be
      interested in doing (startup, shutdown, managing windows, inhibit, etc.)
      
      With this change, all platform specific code has been removed from
      gtkapplication.c and gtkapplicationwindow.c (both of which are now free
      of #ifdefs, except for a UNIX-specific use of GDesktopAppInfo in
      gtkapplicationwindow.c).
      
      Additionally, because of the movement of the property-setting code out
      of GtkApplicationWindow, the _GTK_APPLICATION_ID properties (and
      friends) will be set on non-GtkApplicationWindows, such as dialogs.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=720550
      7fd81cf1
  30. 29 Oct, 2013 1 commit
  31. 17 Oct, 2013 1 commit
  32. 15 Oct, 2013 1 commit
    • Allison Karlitskaya's avatar
      GtkApplication: a new approach to accels · 9a6ee36e
      Allison Karlitskaya authored
      Rework how accels are handled on GtkApplicationWindow.
      
      Instead of having GtkApplication fill the GtkAccelMap which is then used
      by GtkApplicationWindow to create a GtkAccelGroup filled with closures
      that is then associated with the window, do it directly.
      
      GtkApplication now keeps a list of accels and their actions.
      Accelerators on a GtkApplicationWindow ask GtkApplication to execute the
      appropriate action.
      
      This saves a fair bit of complexity and memory use (due to not having to
      create all those closures and accelmap entries).  The new approach also
      supports multiple accels per action (although there is not yet a public
      API for it).
      
      This patch (and the ones before) Reviewed and ACK'd by Matthias Clasen.
      9a6ee36e