1. 15 Jul, 2015 1 commit
    • Allison Karlitskaya's avatar
      GtkApplication: avoid using stale timestamps · a00a5ed2
      Allison Karlitskaya authored
      Avoid using a stale timestamp (from the last user interaction with the
      application) when a message arrives from D-Bus requesting that a new
      window be created.
      In this case the most-correct thing that we can do is to use no
      timestamp at all.
      We modify gdk_x11_display_set_startup_notification_id() to allow a NULL
      value to mean "reset everything" and then call this function
      unconditionally on receipt of D-Bus activation requests.  The result
      will be that a missing desktop-startup-id in the platform-data struct
      will reset the timestamp.
      Under their default configuration metacity and mutter will both map
      windows presented with no timestamp in the foreground.  This could
      result in false-positive, but there is very little we can do about that
      without the original timestamp from the user event.
  2. 02 Jan, 2014 1 commit
  3. 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.
                             |                                  |
                  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
      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.