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. No matching signals for all controls
Forum Updated to NodeBB v4.3 + New Features

No matching signals for all controls

Scheduled Pinned Locked Moved Unsolved General and Desktop
40 Posts 4 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.
  • D Deathcomes

    @mrjj Yes because i have other connect with custom slots

    mrjjM Offline
    mrjjM Offline
    mrjj
    Lifetime Qt Champion
    wrote on last edited by
    #28

    @Deathcomes
    so its only the auto matching that complains ?

    D 1 Reply Last reply
    0
    • mrjjM mrjj

      @Deathcomes
      so its only the auto matching that complains ?

      D Offline
      D Offline
      Deathcomes
      wrote on last edited by
      #29

      @mrjj Correct

      mrjjM 1 Reply Last reply
      0
      • D Deathcomes

        @mrjj Correct

        mrjjM Offline
        mrjjM Offline
        mrjj
        Lifetime Qt Champion
        wrote on last edited by
        #30

        @Deathcomes
        I have no idea why then it must not seem then when running
        QMetaObject::connectSlotsByName(Widget);

        1 Reply Last reply
        0
        • D Offline
          D Offline
          Deathcomes
          wrote on last edited by Deathcomes
          #31

          New info on the problem!

          The failing auto connection of the signals happen when i add the -lQt5Ftp library on

          LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32
          

          which i built from this https://github.com/qt/qtftp

          I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a

          qDebug() << "Click";
          

          Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)

          Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning

          QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()
          

          and the slot is not fired.
          I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library.

          mrjjM JonBJ 2 Replies Last reply
          0
          • D Deathcomes

            New info on the problem!

            The failing auto connection of the signals happen when i add the -lQt5Ftp library on

            LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32
            

            which i built from this https://github.com/qt/qtftp

            I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a

            qDebug() << "Click";
            

            Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)

            Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning

            QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()
            

            and the slot is not fired.
            I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library.

            mrjjM Offline
            mrjjM Offline
            mrjj
            Lifetime Qt Champion
            wrote on last edited by
            #32

            @Deathcomes
            That is really odd as that's a lib and should not really
            interfere with moc and signal findings.
            Maybe it screws up the meta data somehow.

            D 1 Reply Last reply
            0
            • mrjjM mrjj

              @Deathcomes
              That is really odd as that's a lib and should not really
              interfere with moc and signal findings.
              Maybe it screws up the meta data somehow.

              D Offline
              D Offline
              Deathcomes
              wrote on last edited by
              #33

              @mrjj said in No matching signals for all controls:

              Maybe it screws up the meta data somehow.

              How can i check it?

              mrjjM 1 Reply Last reply
              0
              • D Deathcomes

                @mrjj said in No matching signals for all controls:

                Maybe it screws up the meta data somehow.

                How can i check it?

                mrjjM Offline
                mrjjM Offline
                mrjj
                Lifetime Qt Champion
                wrote on last edited by
                #34

                @Deathcomes
                I dont know if we can see that.
                we can check what connectSlotsByName
                does here
                https://code.woboq.org/qt5/qtbase/src/corelib/kernel/qobject.cpp.html#3539

                maybe we could dump the names it sees with and without ftp lib.

                1 Reply Last reply
                0
                • D Deathcomes

                  New info on the problem!

                  The failing auto connection of the signals happen when i add the -lQt5Ftp library on

                  LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32
                  

                  which i built from this https://github.com/qt/qtftp

                  I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a

                  qDebug() << "Click";
                  

                  Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)

                  Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning

                  QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()
                  

                  and the slot is not fired.
                  I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library.

                  JonBJ Offline
                  JonBJ Offline
                  JonB
                  wrote on last edited by
                  #35

                  @Deathcomes
                  One question: why is something as old as Qt 5.2 involved in your build?

                  D 1 Reply Last reply
                  0
                  • JonBJ JonB

                    @Deathcomes
                    One question: why is something as old as Qt 5.2 involved in your build?

                    D Offline
                    D Offline
                    Deathcomes
                    wrote on last edited by
                    #36

                    @JonB We started development on that version and there was never a necessity to upgrade to a newer version.

                    1 Reply Last reply
                    0
                    • D Offline
                      D Offline
                      Deathcomes
                      wrote on last edited by
                      #37

                      It seems (again!) that the problem indeed wasn't the qt5ftp library but the way i built it.
                      You see we use dynamic linking for all the libraries we use in our application (qt and 3rd party) and by mistake i had statically built the qtftp library.
                      This seems that had created some "conflicts" that were the cause of the mentioned problem.

                      mrjjM 1 Reply Last reply
                      0
                      • D Deathcomes

                        It seems (again!) that the problem indeed wasn't the qt5ftp library but the way i built it.
                        You see we use dynamic linking for all the libraries we use in our application (qt and 3rd party) and by mistake i had statically built the qtftp library.
                        This seems that had created some "conflicts" that were the cause of the mentioned problem.

                        mrjjM Offline
                        mrjjM Offline
                        mrjj
                        Lifetime Qt Champion
                        wrote on last edited by
                        #38

                        @Deathcomes
                        Hi
                        Does qt5ftp have any GUI also ?
                        So we could get a name clash or something?

                        D 1 Reply Last reply
                        0
                        • mrjjM mrjj

                          @Deathcomes
                          Hi
                          Does qt5ftp have any GUI also ?
                          So we could get a name clash or something?

                          D Offline
                          D Offline
                          Deathcomes
                          wrote on last edited by
                          #39

                          @mrjj said in No matching signals for all controls:

                          Does qt5ftp have any GUI also ?

                          No as far as i know.

                          mrjjM 1 Reply Last reply
                          0
                          • D Deathcomes

                            @mrjj said in No matching signals for all controls:

                            Does qt5ftp have any GUI also ?

                            No as far as i know.

                            mrjjM Offline
                            mrjjM Offline
                            mrjj
                            Lifetime Qt Champion
                            wrote on last edited by
                            #40

                            @Deathcomes
                            Ok. just wondering how it can make auto connect fail. :)

                            1 Reply Last reply
                            0

                            • Login

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