ServiceJob::setResult already does a emitResult.
Discovered with the assert created in https://phabricator.kde.org/D9862
Details
Details
- Reviewers
broulik - Group Reviewers
Frameworks Plasma - Commits
- R120:4b68374192ac: Avoid a double emitResult()
Diff Detail
Diff Detail
- Repository
- R120 Plasma Workspace
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
A quick search through plasma codebase reveals that setResult followed by emitResult is done quite often. Care to fix these, too? :)
Comment Actions
dataengines/places/setupdevicejob.cpp
dataengines/mpris2/playeractionjob.cpp
dataengines/applicationjobs/jobaction.cpp
Comment Actions
I did a objdump -d to be sure:
dataengines/places/setupdevicejob.cpp
setError is from KJob and it only sets a member value (d->error = errorCode;)
dataengines/mpris2/playeractionjob.cpp
setErrorText is from KJob also and it only sets a member value (d->errorText = errorText;)
dataengines/applicationjobs/jobaction.cpp
The same as the other two.