Re: [Telepathy] Type Conversion Error in PyGI tp-glib
On Mon, Jun 13, 2011 at 16:04, Danielle Madeley
danielle.made...@collabora.co.uk wrote:
On Mon, 2011-06-13 at 15:23 +0200, Tomeu Vizoso wrote:
I'm I doing something wrong? Or is this a bug?
PyGObject is auto-converting your Python int into a GValue, but isn't
choosing the type that the C side expects. What i think should be done
in this case (other than moving tp-glib from dbus-glib to gdbus) is to
give PyGObject a hint of what type should the GValue map to, something
like:
keepalive-interval: GValue(60, GValue.UInt32),
Unfortunately, I don't think that exists, but would be worth asking to
the PyGObject community and checking if a ticket already exists in
bugzilla.gnome.org.
Tomeu is right, this is actually the bug. I was mistakenly confused with
dbus-python.
Tomeu, out of interest would PyGObject handle this better if it was a
GVariant. Now that gjs has gained GVariant support, I think we should
start exposing GVariant-based APIs for gobject-introspection instead of
TpAsv-based ones.
Yup, with variants, PyGObject doesn't try any more to guess the type
that the C side wants, so the user needs to do:
GLib.Variant('i', 42)
GLib.Variant('u', 42)
Regards,
Tomeu
--
Danielle Madeley
Software Developer, Collabora Ltd. Melbourne, Australia
www.collabora.co.uk
___
telepathy mailing list
telepathy@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] ANNOUNCE: Empathy 3.1.2.1
Empathy 3.1.2.1 is now available for download from: http://download.gnome.org/sources/empathy/3.1/ b9a9f9867c7f3b7f2838ce2101c7c376 empathy-3.1.2.1.tar.gz a333ba1df3d095ba3e7fc3c26a016b7e empathy-3.1.2.1.tar.bz2 What is it? === Empathy is a messaging program which supports text, voice, and video chat and file transfers over many different protocols. Empathy is the default chat client in GNOME, and is based on the Telepathy framework, making it easier for other GNOME applications to integrate collaboration functionality. You can visit the project web site: http://live.gnome.org/Empathy What's New? === A small fix release as 3.1.2 was shipping an outdated version of telepathy-yell. We also now depends on telepathy-logger 0.2.10 as the new log viewer was unusable with older versions. Dependencies: • telepathy-logger ≥ 0.2.10 Translations: - Updated gl Translation (Fran Diéguez) - Updated es Translation (Jorge González, Daniel Mustieles) - Updated ug Translation (Abduxukur Abdurixit) - Updated sl Translation (Matej Urbančič) 14 June 2011 Empathy team ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] How do I receive channels in an observer client?
I think I'm missing a step to help my observer receive incoming media channels. Here's what I've done. 1) I've registered an Account with the AccountManager 2) Via the Account I've requested the presence to be Available. If I'm not mistaken this automatically sets up a connection. 3) I've initialized a simple observer client and registered it with the AccountManager and it has a name on the bus. Code for the observer client: http://pastebin.com/zvEc8HeK Yet, I can't receive any media channels. P.S. The only time I can receive media channels is when I have Empathy running. What step am I missing? Do I need to initialize and prepare a ChannelDispatcher? I have _neither_ an approver or handler client implemented yet. Does this matter? Thanks ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] How do I receive channels in an observer client?
On Tue, 14 Jun 2011 at 10:11:06 -0400, Mystilleef wrote: Yet, I can't receive any media channels. ... I have _neither_ an approver or handler client implemented yet. Does this matter? I don't know exactly what you mean by can't receive, but if you mean my contacts see me as not callable and/or can't call me and you're on XMPP, that may be because it's the Handler that tells Gabble which NAT traversal mechanisms it understands. Without a Handler, Gabble is aware that it doesn't support any NAT traversal mechanisms, and tells your contacts that it doesn't support any; your contacts interpret that as can't be called. Another possibility is this MC bug: https://bugs.freedesktop.org/show_bug.cgi?id=29022 in which channels for which you don't have a Handler aren't given to Observers either, on the basis that MC is about to close the channel anyway. I think that's a bug - it should tell the Observers, wait for them all to respond, *then* close the channel - but the patches to fix it haven't been merged yet. P.S. The only time I can receive media channels is when I have Empathy running. While it's running, Empathy provides a StreamedMedia Handler. You're not going to be usefully callable unless you have some sort of Handler for the channel, so if you don't want to use the one from Empathy, you'll have to implement another. As a quick hack first implementation, it could just accept the channel and not do anything with it... S ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] ANNOUNCE: telepathy-sofiasip 0.6.8
Telepathy-SofiaSIP stable release 0.6.8, homage to World's Toughest Fixes release, is now available. Tarball: http://telepathy.freedesktop.org/releases/telepathy-sofiasip/telepathy-sofiasip-0.6.8.tar.gz Signature: http://telepathy.freedesktop.org/releases/telepathy-sofiasip/telepathy-sofiasip-0.6.8.tar.gz.asc New in this release: - Refactored handling of local codec information to avoid excessive re-INVITEs. - Remove non-intersecting local codecs from any further SDP negotiations (fd.o #30434). Enjoy, Mikhail ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] How do I receive channels in an observer client?
On Tue, Jun 14, 2011 at 10:31 AM, Simon McVittie simon.mcvit...@collabora.co.uk wrote: On Tue, 14 Jun 2011 at 10:11:06 -0400, Mystilleef wrote: Yet, I can't receive any media channels. ... I have _neither_ an approver or handler client implemented yet. Does this matter? I don't know exactly what you mean by can't receive, but if you mean my contacts see me as not callable and/or can't call me and you're on XMPP, that may be because it's the Handler that tells Gabble which NAT traversal mechanisms it understands. Without a Handler, Gabble is aware that it doesn't support any NAT traversal mechanisms, and tells your contacts that it doesn't support any; your contacts interpret that as can't be called. I meant receiving incoming SIP calls. Another possibility is this MC bug: https://bugs.freedesktop.org/show_bug.cgi?id=29022 in which channels for which you don't have a Handler aren't given to Observers either, on the basis that MC is about to close the channel anyway. I think that's a bug - it should tell the Observers, wait for them all to respond, *then* close the channel - but the patches to fix it haven't been merged yet. Aha! Most likely the same problem I'm having. P.S. The only time I can receive media channels is when I have Empathy running. While it's running, Empathy provides a StreamedMedia Handler. You're not going to be usefully callable unless you have some sort of Handler for the channel, so if you don't want to use the one from Empathy, you'll have to implement another. As a quick hack first implementation, it could just accept the channel and not do anything with it... Thanks a lot. I'll implement a handler. ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
