No way to choose a peer other than default from QML bindings

Bug #1236932 reported by Ken VanDine
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
content-hub (Ubuntu)
Fix Released
High
Ken VanDine

Bug Description

In the QML bindings, there is no way to construct a peer and knownSourcesForType doesn't return a QML friendly list of peers. This limits the QML bindings to only using default peer for a type.

Related branches

affects: content-hub → content-hub (Ubuntu)
Changed in content-hub (Ubuntu):
assignee: nobody → Günter Schwann (schwann)
Changed in content-hub (Ubuntu):
importance: Undecided → High
description: updated
Changed in content-hub (Ubuntu):
assignee: Günter Schwann (schwann) → Ken VanDine (ken-vandine)
Changed in content-hub (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package content-hub - 0.0+14.04.20131025-0ubuntu1

---------------
content-hub (0.0+14.04.20131025-0ubuntu1) trusty; urgency=low

  [ Ken VanDine ]
  * return a QVariantList from knownSourcesForType so the QML bindings
    can expose a list of peers, fixes (LP: #1236932). (LP: #1236932)
  * Added qdoc docs for QML bindings.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 63
 -- Ubuntu daily release <email address hidden> Fri, 25 Oct 2013 11:04:43 +0000

Changed in content-hub (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.