Avoid "QObject::disconnect: Unexpected null parameter" error on application stop
ClosedPublic

Authored by mkoller on Jul 13 2018, 12:47 PM.

Details

Summary

When I use the MarbleWidget in my application - or even using my installed marble app (openSuse 42.3), I get:
QObject::disconnect: Unexpected null parameter
on exit.

I found this to be the Annotation plugin using a nullptr in m_marbleWidget
Since in the dtor there is already a check for this pointer being 0, I moved the disconnect there.

Diff Detail

Repository
R34 Marble
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
mkoller created this revision.Jul 13 2018, 12:47 PM
Restricted Application added projects: Marble, KDE Edu. · View Herald TranscriptJul 13 2018, 12:48 PM
Restricted Application added subscribers: kde-edu, marble-devel. · View Herald Transcript
mkoller requested review of this revision.Jul 13 2018, 12:48 PM
sanjibanb accepted this revision as: sanjibanb.Aug 29 2018, 6:57 AM
This revision is now accepted and ready to land.Aug 29 2018, 6:57 AM
This revision was automatically updated to reflect the committed changes.