exposing dbus error names on the glib client side

[Ross Burton]

On Sun, 2005-06-26 at 13:04 -0400, Colin Walters wrote:
> I see your point; that makes sense.  In the case where you're just
> propagating the GError up which eventually ends up in some dialog (which
> is usually bad, but...) at least the user will see a human-readable
> error string instead of like org.freedesktop.Hal.DeviceAlreadyLocked or
> whatever.

When the bindings are using the async machinery server-side,
dbus_g_error_set() can't be used as dbus_g_method_return() takes a new
GError*.  Attached is a patch to add dbus_g_error_new(), which does as
you'd expect.

Ross
-- 
Ross Burton                                 mail: ross at burtonini.com
                                          jabber: ross at burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: dbus.diff
Type: text/x-patch
Size: 1691 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20050627/00231df7/dbus.bin