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.
Details
Details
Still builds (WITH_KDE=ON & BUILD_MARBLE_EXAMPLES=ON) and marble app still
works.
Diff Detail
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.
Comment Actions
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.