[Solved] Use of signal-slot connect in Windows 10

[koahnig]

@JKSH
Yes, I have already seen this yesterday. Thanks for suggesting.

[koahnig]

@SGaist @JKSH @mrjj

Just for closing the issue here. I have the new syntax for connect. I love it, even though it has "drawbacks" of different functionality according the documentation presented by JKSH above. For me it is perfect! Thanks again for pointing towards teh new syntax.

[mrjj]

May I humbly suggest to follow your signature ? ;)

[koahnig]

@mrjj
Actually, my initial problem is not solved. ;)
The warning at wrong connects still seems to be gone. Which might be a either a problem with my installation or a bug in Qt.

[mrjj]

@koahnig
oh. Well. My bad :)
I tried to install win 10 to but it wont upgrade.
Pretty strange what ever made it stop to display.

[JKSH]

@koahnig said:

The warning at wrong connects still seems to be gone.

I get the error message for wrong connections, and I'm using Qt 5.5.1 MinGW 4.9.2 32-bit and Qt 5.4.2 MSVC 2013 32-bit on Windows 10 Pro 64-bit.

Does qDebug() and qWarning() work for you?

[koahnig]

@JKSH said:

I get the error message for wrong connections, and I'm using Qt 5.5.1 MinGW 4.9.2 32-bit and Qt 5.4.2 MSVC 2013 32-bit on Windows 10 Pro 64-bit.

Does qDebug() and qWarning() work for you?

I am using qDebug all the time. It does work.

[JKSH]

@koahnig said:

I am using qDebug all the time. It does work.

How about qWarning()?

[koahnig]

@JKSH
qWarning is also working.
However, your last question brought up a clue of what might have been the case.

I am using a message handler for redirecting the output of qDebug. It allows to ignore all output, to store all to a file and/or to the screen.
Since there is a lot of output, the screen output is slowing down dramatically. Therefore, I have redirected the output only to the file. The assert was probably kicking in before the message was written to the file. I have seen this with other output before, but never with the warning for connection failures (Probably I had also screen output then).

Anyway even when the problem was between chair and keyboard, it was good to have the discussion. Otherwise I would not have learnt about the new syntax.

Thanks again.

[koahnig]

A point I have missed in my previous response.

I have written a small test this time.

#include "Clas.h"
#include <QTimer>
#include <QDebug>

Clas::Clas(QObject *parent) :
    QObject(parent)
{
    QTimer *timea = new QTimer ( this );
    connect ( timea, SIGNAL ( timerout() ), this, SLOT (sltQuit() ) );
    qDebug() << "debug";
    qWarning() << "warning";
}
void Clas::sltQuit()
{
}

and here is the output

Qt: Untested Windows version 10.0 detected!
QObject::connect: No such signal QTimer::timerout() in ..\..\Test\CheckConnect\Clas.cpp:9
debug
warning

So it is working perfectly also on windows 10 with MinGW version Qt 5.4.1.

[SGaist]

Just saw something: the warning's right, the signal is timeout not timerout

[JKSH]

Great! :)

[koahnig]

@SGaist
Yes. That was intensional. I just tested that my installation is still providing the message.
Thanks a lot anyway.