| Summary: | Can't support multiple requestable channel classes for the same channel type | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Jonny Lamb <jonny.lamb> |
| Component: | tp-python | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | Keywords: | patch |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | http://git.collabora.co.uk/?p=user/jonny/telepathy-python.git;a=shortlog;h=refs/heads/misc-for-conference | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
I've fixed this in my misc-for-conference branch. I've already asked Olivier to review it. For reference, my conference butterfly branch uses this new function. Fixed in 0.15.17. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
The drunken haze I was under when I implemented the Requests interface and the channel manager assisted in adding an annoying oversight into the RequestableChannelClasses retrieving. For example: fixed = {telepathy.CHANNEL_INTERFACE + '.ChannelType': telepathy.CHANNEL_TYPE_TEXT, telepathy.CHANNEL_INTERFACE + '.TargetHandleType': dbus.UInt32(telepathy.HANDLE_TYPE_CONTACT)} self._implement_channel_class(telepathy.CHANNEL_TYPE_TEXT, self._get_text_channel, fixed, [CHANNEL_INTERFACE_CONFERENCE + '.InitialChannels']) This is great if the only RCC you want for text channels is: ({ChannelType: TEXT, TargetHandleType: CONTACT}, [InitialChannels]) But that's not always the case. Sigh.