I've seen this warning now on both signals and slots and since our code isn't crashing this seems like a reasonable explanation and needs special attention.
https://stackoverflow.com/questions/53527950/is-it-safe-to-connect-a-signal-to-a-pure-virtual-slot-in-a-constructor-of-a-base
I know it is happening with the newer connect style, I can't remember if we had an example using the older style.
With this statement the special treatment should extend to more than signals and slots and if in a connect then maybe suppress
https://wiki.qt.io/New_Signal_Slot_Syntax
It is possible to connect to any member function of QObject, not only slots.
With --library=qt, I don't get the pureVirtualCal warning. Otherwise, I do.
--library=qt
Thanks, we'll look into that.
Log in to post a comment.
I've seen this warning now on both signals and slots and since our code isn't crashing this seems like a reasonable explanation and needs special attention.
https://stackoverflow.com/questions/53527950/is-it-safe-to-connect-a-signal-to-a-pure-virtual-slot-in-a-constructor-of-a-base
I know it is happening with the newer connect style, I can't remember if we had an example using the older style.
With this statement the special treatment should extend to more than signals and slots and if in a connect then maybe suppress
https://wiki.qt.io/New_Signal_Slot_Syntax
It is possible to connect to any member function of QObject, not only slots.
With
--library=qt
, I don't get the pureVirtualCal warning. Otherwise, I do.Thanks, we'll look into that.