Seems I'm writing a patch for TpQt. Andrunko gave me a bit of help in doing this on IRC.
I've managed to implement it directly using the low level bindings and some horrific hacks. So far everything is going great except for one issue. I've written code that when you press a button in the plasmoid it delegates. Works perfectly, the main text-ui launches gets a new tab with the chat. However, my plasmoid still has a valid channel and as it thinks it's a handler so will carry on happily acking messages whenever it wants to. 1) Is it up to the client code to throw away its references to the text channel after it successfully delegates? 2) Can the client keep the channel, but know to effectively act like an observer? If so is there any way to find out if a channel is being handled by our application or not? I ask because after I call delegateChannels when I browse my original handler in dbusviewer Client.Handler/HandledChannels still seems to have the original channel. This seems wrong? Also when I delegateChannels can I pass hints? In the process of this contact list -> plasmoid -> textUI approach any hints now get lost. We use a special KDE channel hint to work round a kwin "bug", and now that's not working. It seems limiting to not be able to pass them. Thanks for all your help so far! Dave _______________________________________________ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy