cannot connect to limitationsUpdated signal

Bug #1547194 reported by Lorn Potter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-network (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In connectivity.h, the limitationsUpdated signal is declared as such:
  void limitationsUpdated(const QVector<Limitations>&);

When I use this syntax to connect:
    connect(ns.data(),SIGNAL(limitationsUpdated(const QVector<Limitations>&)),
                             this,SLOT(limitationsUpdated(const QVector<Limitations>&));

I get this error when building:

tstconnectivity.h:21:43: error: ‘Limitations’ was not declared in this scope
     void limitationsUpdated(const QVector<Limitations>&);

When I try:
    connect(ns.data(),SIGNAL(limitationsUpdated(const QVector<connectivityqt::Connectivity::Limitations>&)),
                             this,SLOT(limitationsUpdated(const QVector<connectivityqt::Connectivity::Limitations>&));
It builds, but I get this error when running:
2016-02-18T17:52:55 (unknown:0) - QObject::connect: No such signal connectivityqt::Connectivity::limitationsUpdated(const QVector<connectivityqt::Connectivity::Limitations>&)

The signal should probably be declared:
  void limitationsUpdated(const QVector<connectivityqt::Connectivity::Limitations>&);

with connectivityqt::Connectivity:: just as the statusUpdated

Tags: patch

Related branches

Revision history for this message
Lorn Potter (lorn-potter) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "connectivityqt-limitations.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-network - 0.7.1+16.04.20160511-0ubuntu1

---------------
indicator-network (0.7.1+16.04.20160511-0ubuntu1) xenial; urgency=medium

  [ Pete Woods ]
  * Fix limitations property (LP: #1547194)
  * Remember hotspot UUID
  * Store information about which device we are using in a member
    variable
  * Wait for hotspot device to be ready, not just present (LP: #1579221)
  * Wait for hotspot to finish activating

  [ Tony Espy ]
  * hotspot: Don't create NM ipv4 settings with empty values. (LP:
    #1579221)

 -- Tony Espy <email address hidden> Wed, 11 May 2016 16:57:39 +0000

Changed in indicator-network (Ubuntu):
status: New → 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.