Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. [Resolved] Object::connect: No such signal QNetworkAccessManager::sslErrors
Forum Updated to NodeBB v4.3 + New Features

[Resolved] Object::connect: No such signal QNetworkAccessManager::sslErrors

Scheduled Pinned Locked Moved General and Desktop
4 Posts 2 Posters 5.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    adewang
    wrote on 5 Dec 2011, 09:43 last edited by
    #1

    Hi all:

    This problem is driving me crazy..

    I installed openssl, then I compiled qt 4.7.4 with -openssl option.
    but when i run my application ,always get this error info:

    Object::connect: No such signal QNetworkAccessManager::sslErrors

    Does anyone knows how to resolve it?
    Is there any other configuration needed?

    Thanks.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andre
      wrote on 5 Dec 2011, 12:01 last edited by
      #2

      Could you show your actual connect statement?

      1 Reply Last reply
      0
      • A Offline
        A Offline
        adewang
        wrote on 6 Dec 2011, 01:01 last edited by
        #3

        @ connect(m_page.networkAccessManager(), SIGNAL(sslErrors ( QNetworkReply * reply, const QList<QSslError> & errors )), this, SLOT(handleSslErrors(QNetworkReply * reply, const QList<QSslError> & errors)));
        @

        1 Reply Last reply
        0
        • A Offline
          A Offline
          adewang
          wrote on 6 Dec 2011, 01:11 last edited by
          #4

          I know what leads to this problem...
          Should not write the formal parameter names in the connect statement.
          The follow statement works.

          @ connect(m_page.networkAccessManager(), SIGNAL(sslErrors(QNetworkReply , const QList<QSslError> &)), this, SLOT(handleSslErrors(QNetworkReply, const QList<QSslError> &)));
          @

          Thanks, Andre.

          1 Reply Last reply
          0

          1/4

          5 Dec 2011, 09:43

          • Login

          • Login or register to search.
          1 out of 4
          • First post
            1/4
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved