Use consistently Q_SIGNALS/Q_SLOTS (and set QT_NO_SIGNALS_SLOTS_KEYWORDS)
ClosedPublic

Authored by kossebau on May 13 2016, 3:56 PM.

Details

Summary

Currently there is a mix of both signals/slots and Q_SIGNALS/Q_SLOTS.
Given Marble is also promoted as library, it seems to make sense to
standardize on Q_SIGNALS/Q_SLOTS, and for consistency do that project-wide,
not just for the lib API.
Adding QT_NO_SIGNALS_SLOTS_KEYWORDS should prevent any regressions here.

Test Plan

Still builds (WITH_KDE=ON & BUILD_MARBLE_EXAMPLES=ON) and marble app still
works.

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.
kossebau updated this revision to Diff 3811.May 13 2016, 3:56 PM
kossebau retitled this revision from to Use consistently Q_SIGNALS/Q_SLOTS (and set QT_NO_SIGNALS_SLOTS_KEYWORDS).
kossebau updated this object.
kossebau edited the test plan for this revision. (Show Details)
kossebau added reviewers: rahn, nienhueser.
nienhueser accepted this revision.May 14 2016, 6:26 AM
nienhueser edited edge metadata.

Looks good to me. I just hope it does not confuse newcomers if they find signals/slots keywords not to work if they work on new code.

This revision is now accepted and ready to land.May 14 2016, 6:26 AM
This revision was automatically updated to reflect the committed changes.