1. 05 Jun, 2015 1 commit
    • Allison Karlitskaya's avatar
      GActionGroupExporter: flush queue on requests · 865ce79c
      Allison Karlitskaya authored
      In order to maintain a logical stream of events, we need to make sure we
      flush and queued change notifications before responding to any requests
      for information from clients.
      If we don't do this, it's possible that we emit an 'add' event that was
      queued at the time of a 'DescribeAll' call _after_ the reply to that
      call (which already contained the description of the new action).
      In practice, this is not only logically incorrect, but it can also cause
      problems.  If a change to action 'state' or 'enabled' occurs after the
      DescribeAll but before the signal has been dispatched, it will be
      ignored because an 'add' signal is already pending.  When that add
      signal is sent, it will contain the correct data, but the receiver will
      ignore it because it already saw the action in the DescribeAll reply.
  2. 02 Jul, 2014 1 commit
  3. 27 Mar, 2014 1 commit
  4. 31 Jan, 2014 1 commit
  5. 08 Jan, 2014 1 commit
  6. 29 Oct, 2013 2 commits
  7. 02 Nov, 2012 1 commit
  8. 21 Feb, 2012 1 commit
  9. 20 Dec, 2011 1 commit
  10. 17 Dec, 2011 2 commits
  11. 16 Dec, 2011 1 commit
    • Allison Karlitskaya's avatar
      GDBusActionGroup: add static platform registration · fcc9902e
      Allison Karlitskaya authored
      We provide a mechanism by which a 'platform' (eg: Gtk) can register some
      hook functions to be called to collect platform-data at the point of
      sending an outgoing action activation request and also to inform the
      platform of this data on incoming requests (before and after dispatching
      the actual request).
      This can be used for forwarding timestamp and startup-notification
      information (as is presently done in GApplication) but the before/after
      hook could also be used for acquiring/releasing the Gdk lock or other
      similar things.
  12. 12 Dec, 2011 1 commit
    • Allison Karlitskaya's avatar
      GActionGroupExporter: stop using signal IDs · 93f17967
      Allison Karlitskaya authored
      GDBusConnection recently changed to dispatching its GDestroyNotify calls
      from an idle instead of on-the-spot.  Under the previous regime, we
      would destroy-notify the action group export of a GtkApplicationWindow
      at the point it was removed from the application (ie: slightly before
      being disposed).
      With the destroy notify now deferred to an idle, the window has already
      been disposed, so the signal handlers have already been disconnected.
      Avoid the problem by dropping our use of signal IDs and just do
      g_signal_handlers_disconnect_by_func(), which doesn't complain if there
      is no connection.
  13. 08 Dec, 2011 9 commits