1. 20 Dec, 2018 1 commit
  2. 12 Jan, 2018 1 commit
  3. 29 May, 2017 1 commit
  4. 16 Mar, 2017 1 commit
  5. 22 Nov, 2016 1 commit
  6. 07 Nov, 2015 1 commit
    • Philip Withnall's avatar
      glib: Add missing (nullable) and (optional) annotations · 25a7c817
      Philip Withnall authored
      Add various (nullable) and (optional) annotations which were missing
      from a variety of functions. Also port a couple of existing (allow-none)
      annotations in the same files to use (nullable) and (optional) as
      appropriate instead.
      
      Secondly, add various (not nullable) annotations as needed by the new
      default in gobject-introspection of marking gpointers as (nullable). See
      https://bugzilla.gnome.org/show_bug.cgi?id=729660.
      
      This includes adding some stub documentation comments for the
      assertion macro error functions, which weren’t previously documented.
      The new comments are purely to allow for annotations, and hence are
      marked as (skip) to prevent the symbols appearing in the GIR file.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=719966
      25a7c817
  7. 18 Aug, 2015 1 commit
  8. 28 Oct, 2014 1 commit
    • Owen W. Taylor's avatar
      GDBusInterfaceVTable: clarify memory handling for the method() virtual function · 66fc112c
      Owen W. Taylor authored
      There are two consistent interpretations that could be taken for memory
      handling of the 'invocation' parameter passed to the method_call() virtual
      function of GDBusInterfaceVTable
      
       - A reference is passed (transfer full) to the method_call() virtual function,
         and that reference is then passed (transfer full) to the return_value/error
         functions on GDBusMethodInvocation.
       - An internal reference is retained from the point where method_call() is called
         until the return_value/error function is called.
      
      Since the return_value/error functions were already marked (transfer full),
      we use the first interpretation, annotate the invocation parameter of
      method call as (transfer full) and describe this in the documentation, along
      with the idea that you are always supposed to call one of the return_value/error
      functions.
      
      See bug 738122 for the leak this caused in GJS.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=738259
      66fc112c
  9. 02 Mar, 2014 1 commit
  10. 31 Jan, 2014 1 commit
  11. 23 Jun, 2013 1 commit
    • Dieter Verfaillie's avatar
      docs: fix GTK-Doc build · fdc93791
      Dieter Verfaillie authored
      cd html && gtkdoc-mkhtml $mkhtml_options  gio ../gio-docs.xml
      ../xml/gdbusconnection.xml:2063: parser error : Opening and ending tag mismatch: literal line 2062 and para
      </para>
             ^
      fdc93791
  12. 22 Jun, 2013 1 commit
    • Allison Karlitskaya's avatar
      GDBusConnection: allow async property handling · f754c4e8
      Allison Karlitskaya authored
      The existing advice in the documentation to "simply" register the
      "org.freedesktop.DBus.Properties" interface if you want to handle
      properties asynchronously is pretty unreasonable.  If you want to handle
      this interface you have to deal with all properties for all interfaces
      on the path, and you have to do all of the checking for yourself.  You
      also have to provide your own introspection data.
      
      Introduce a new convention for dealing with properties asynchronously.
      
      If the user provides NULL for their get_property() or set_property()
      functions in the vtable and has properties registered then the
      properties are sent to the method_call() handler.  We get lucky here
      that this function takes an "interface_name" parameter that we can set
      to "org.freedesktop.DBus.Properties".
      
      We also do the user the favour of setting the GDBusPropertyInfo on the
      GDBusMethodInvocation for their convenience (for much the same reasons
      as they might want the already-available GDBusMethodInfo).
      
      Add a testcase as well as a bunch of documentation about this new
      feature.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=698375
      f754c4e8
  13. 13 Jan, 2013 1 commit
  14. 28 Dec, 2012 1 commit
  15. 06 Jun, 2012 1 commit
  16. 26 May, 2012 1 commit
  17. 21 Jul, 2011 1 commit
  18. 09 Sep, 2010 2 commits
  19. 25 Aug, 2010 1 commit
  20. 06 Aug, 2010 1 commit
  21. 19 Jul, 2010 3 commits
  22. 15 Jul, 2010 3 commits
  23. 14 Jul, 2010 2 commits
  24. 07 Jul, 2010 3 commits
  25. 30 Jun, 2010 2 commits
  26. 22 Jun, 2010 1 commit
    • David Zeuthen's avatar
      GDBus: update padding · 2be38f69
      David Zeuthen authored
      Add lots of padding for public class structures. Notably, we seemed to
      lack any padding whatsoever in the GDBusMessageClass struct (spotted
      by Dan Winship). Also switch to using
      
       gpointer padding[N];
      
      instead of
      
       void (*_g_reserved1) (void);
       ...
       void (*_g_reservedN) (void);
      Signed-off-by: default avatarDavid Zeuthen <davidz@redhat.com>
      2be38f69
  27. 21 Jun, 2010 1 commit
  28. 07 Jun, 2010 1 commit
    • Matthias Clasen's avatar
      Merge the wip/gapplication branch · 6427e937
      Matthias Clasen authored
      This adds a GApplication object to GIO, which is the core of
      an application support class, supporting
      - uniqueness
      - exporting actions (simple scripting)
      - standard actions (quit, activate)
      
      The implementation for Linux uses D-Bus, takes a name on the
      session bus, and exports a org.gtk.Application interface.
      
      Implementations for Win32 and OS X are still missing.
      6427e937
  29. 06 Jun, 2010 1 commit
  30. 24 May, 2010 1 commit
    • Allison Karlitskaya's avatar
      GDBusConnection.call(): add 'reply_type' argument · 3160bcad
      Allison Karlitskaya authored
      This allows the caller to specify the reply type that they are expecting
      for this call.  If the reply comes back with the wrong type, GDBus will
      generate an appropriate error internally.
      
        - add a GVariantType * argument to g_dbus_connection_call() and
          _call_sync().
      
        - move the internal API for computing message types from introspection
          data to be based on GVariantType instead of strings.  Update users
          of this code.
      
        - have GDBusProxy pass this calculated GVariantType into
          g_dbus_connection_call().  Remove the checks done in GDBusProxy.
      
        - Update other users of the code (test cases, gdbus-tool, GSettings
          tool, etc).  In some cases, remove redundant checks; in some other
          cases, we are fixing bugs because no checking was done where it
          should have been.
      
      Closes bug #619391.
      3160bcad
  31. 13 May, 2010 1 commit